Release and Update Data structure - Githubissues

iron-bound-designs / exchange-addon-licensing

iThemes Exchange Licensing Add-on

GNU Affero General Public License v3.0

6 stars 2 forks source link

Release and Update Data structure #32

Closed TimothyBJacobs closed 9 years ago

TimothyBJacobs commented 9 years ago

Releases and upgrades will be stored in separate tables.

Releases

ID. Unique, auto-generated, primary key.
product. ID of the corresponding product.
download. ID of the corresponding Exchange download post.
version. Varchar storing the version number.
status. Varchar of the status.
type. Varchar of the Release type.
changelog. Text of what changed just in this version.
start_date. Date and time of when the releases was started.

Updates

ID. Unique, auto-generated, primary key.
activation. ID of the activation record.
release. ID of the corresponding release.
date. Time of the upgrade.

TimothyBJacobs commented 9 years ago

Tables have been implemented, next step is to determine what indexes are necessary on the upgrades table.

TimothyBJacobs commented 9 years ago

Indexes added.