Relation system

Presentation by Ber Kessels, see background about creating a generalized relationship model.

Outline of the relation system presentation.

• Content




• What: General relations


• Why: Standards


• How: the route and todos




• What: General relations




• General relations system, instead of scattered efforts to do the same


• One database table, to store all relations data


• A set of APIs to get, update, alter, insert, delete etc. relations or
  relation trees




• Why: Standards




• In core we see four mayor tree building system completely incompatible.




• Not indicating that this will replace these.




• In contribs there are three relations modules.


• In contribs there are at least 10 potential use cases of these APIS.




• they no longer need a mysql file


• they can become much smaller


• They are much easier to build and maintain


• they can use eachothers data




• Questions were raised




• A general system will never be as optimal as private systems opimised
  fr their task.






• How: the route and todos




• Now testing with clipper and shazamgallery.




• clipper: node <-> node


• shazamgallery: singular parent <->child




• Decide on a single table structure


• Decideon what sort of API:




• .inc


• .module


• contribs vs core.




• Decide on the required APIs

Notes

Please add your notes below...