Restructure Database
Closed this issue · 4 comments
GoogleCodeExporter commented
The table structure needs to be redesigned from the ground up to allow
expansion and maintainability. Up to this point we have added new tables based
solely on immediate feature needs, but continuing this pattern will render the
addition of new features unmanageable. For example, are storing the same
information (show info) in two separate tables (download and recent shows). We
need to normalize the data structure before we implement any new features that
may require database changes.
Original issue reported on code.google.com by sedena...@gmail.com on 23 Nov 2010 at 3:43
GoogleCodeExporter commented
Original comment by sedena...@gmail.com on 23 Nov 2010 at 4:08
- Added labels: Priority-Medium
- Removed labels: Priority-High
GoogleCodeExporter commented
Original comment by andrewpearson@gmail.com on 23 Nov 2010 at 3:45
- Added labels: Priority-High
- Removed labels: Priority-Medium
GoogleCodeExporter commented
Original comment by sedena...@gmail.com on 24 Nov 2010 at 6:07
- Changed state: Started
GoogleCodeExporter commented
Original comment by sedena...@gmail.com on 9 Dec 2010 at 5:04
- Changed state: Fixed