Closed haubourg closed 6 years ago
You would move existing stuff to qwat_api ?
@3nids
I just opened a ticket to have on going actions in the qwat's dashboard, no action required here :)
We've been discussing about thick database practices a few times. A refactor to use only views, limit cascaded views to 2 levels max, limit triggers on tables when calculated views can do the work, store and organize stored procedures in a dedicated schema, is always a good thing. I'd like to see this happen in the future in QWAT since jumping into QWAT DB structure and dev seems not so easy in the current state.
I am unassigning me to remove it from my todo list. I guess the issue can be closed, but I let you do that part!
Yep, done thanks
The database structure will follow the QWAT's one with :
_od : schema for ordinary data (actual user data) _vl: value lists *_sys: system tables like version for PUM, audit logs
To be noted, QGEP now has a qgep_api schema which stores the stored procedure. This is a good practice that would be nice to have in QWAT too.