Major DataBase overhaul and restructuring [$20]
Created by: E3V3A
As we have noticed in many recent issues and many past discussions, there is a terrible urgent need to restructure our original database (DB). This DB was originally made for our very first attempts in building this app. However, we've come to realize that the way it is used and structured and how its tables are internally labelled is really confusing at best. It was made according to very weak documentation and poor understanding of what we actually needed.
After several weeks of thinking about this, on and off, I've come to the point where it's time to get it done. Here is a brand new proposal that should cover most features in the near future and hopefully most of the beta stage life-time.
This is the way we will do it:
- I finish the DB documents and table ER diagram, then
- you guys make a critical re-view and feedback.
- I make the required updates, if any, and go back to (1), else
- we re-code the DB into app.
NOTE: I suggest keeping the old tables while adding the new ones, to maintain simple and progressive migration.
There will surely be loads of questions surrounding this, but I think I might have covered most of it in the (still to be finished) documents:
-
General DB functional overview -
Detailed DB tables Descriptions -
Default DB data
Then there will be new App help pages and an FAQ, to be implemented inside app. (Separate issue.)
-
General App functionality -
Internal App help pages -
Internal App FAQ -
TBA
Here are the old currently used DB tables:
Here are the NEW DB tables:
UPDATED: 2015-07-31
Reference Issues: These are issues that directly depend on these tables. #13 (closed), #69 (closed),#71, #91, #93, #97, #100 (closed), #117 (closed), #176, #201, (#203 (closed) ?),
More descriptions will be added below.
There is a $10 open bounty on this issue. Add to the bounty at Bountysource.