Skip to content
This repository has been archived by the owner on Jan 25, 2021. It is now read-only.

Update system #64

Open
brunnopleffken opened this issue Mar 10, 2016 · 1 comment
Open

Update system #64

brunnopleffken opened this issue Mar 10, 2016 · 1 comment

Comments

@brunnopleffken
Copy link
Owner

With the v0.9 to be released in the coming days with new features (and ever closer to the final version), it is necessary to develop a practical and functional update system.

The main requirement of the future system update is: the community administrator can update to the latest version, regardless of which version he's currently using. The steps involve identifying the current version of the forum system and the latest version; define how many migration steps will be made in the database, and perform all the migration steps.

The expectation is that the new system updates to be deployed in version 0.10, so the development of version 0.10 will be fully focused on this new feature.

@johnforte
Copy link
Contributor

Hello, you really should go with a more abstract database, if you plan on doing auto updating, too many issues can a raise with an unstable database, or even foreign key constraints.

So for example doing...

Member table which includes, id, username, HashPassword, CreatedDate.

Then you would have a Member_data table, which would have member_id, variable, value. This would give your update script more scalability.

@brunnopleffken brunnopleffken mentioned this issue Apr 12, 2017
8 tasks
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants