Support for cosedimenting components

[doluk]

No description provided.

[ehb54]

@doluk
This seems ok to merge, waiting for an update on the us3_sql pull request.

Note - updating any system with database changes generally requires careful handling (either upgrading the db with a standard procedure or manually inserting the new tables and stored procedures)

[doluk]

Should I write an update procedure for this too? Where should I put it if so? @ehb54

[ehb54]

Should I write an update procedure for this too? Where should I put it if so? @ehb54

@doluk
Specific databases can be in various states (generally sync'd with a specific us3_sql git commit - occasionally with some hand patches - particularly on dev servers). Perhaps a subtree under us3_sql/patches/something-descriptive
with a README.md describing the usage & applicability.

Note this is not a requirement, we have established procedures for the general case. However, for testing, this will save us time (established procedures require exporting, dropping, recreating & reimporting for each database. automated, but time consuming and requires idle users and jobs)

[doluk]

In this case the update only consists in adding new tables and procedures. I don't know if the time is worth it this time. If you want one, I can do it (after I figured out what the good practice for such things is xD)

[doluk]

@ehb54
I added in the pull request an sql file containing all stuff I changed so it is just executing this file. Let me know if you want something changed (or change it yourself, if you want)