[#137] - Database Schema Cleanup
- Closed
- 5 Aug 2013
- Medium
- Build: framework
- # 137
- Diff
- joomla:dbSchema
- Success default The Travis CI build passed Details
User tests: Successful: Unsuccessful:
This is a first cut at cleaning up the database schema some. Overall changes:
- Remove unused
#__languagesand#__sessiontables - Adding FKs as appropriate
- Reordering the table order in the installer to work with the FKs
The last unused table is the #__categories table which was being used for field data in the item submit/edit form in the Platform version of the app. Left to decide is whether we still use this data or if we just drop it in favor of the pure Markdown interface in place now.
Image below shows the altered schema (as compared to the one I posted to G+ the other day)
Alright, both of those tables are gone now, which leaves the relations code/schema.
Looking at the relations stuff, it looks like the only reference remaining to that code is in IssueModel where the table is joined to but the data is unused. So we could either (re-)implement that stuff (I'm in favor of that personally) or just drop that little bit out and revisit the subject down the road.
Fine with me, let me see if I find some time to re-implement the relations thingy.
-
Umm, I somewhat missed your post on G+...
Yes I think we should scratch the custom fields idea for now and go with "markdown". The mayor goal with this approach was reusing com_categories, which is gone now (RIP).
Along with the
#__categoriestable, this would also make#__tracker_fields_values. obsoleteAnother thing that might need review is the "issue relations" (#76) thing, which is currently not enabled but the code is still present (most of it I think).
This would affect
#__issues_relations_typesand the fieldsrel_idandrel_typein#__issues