[DRAFT] rdbs scheme development

Datamodel

Adjust the model

• Master records have a common subset of fields for maintenance issues:

  • record_id: id is unique within table
  • active/status: deletions change to 0 for inactive state due to foreign keys. Usefull if one Vendor should be deleted, not uses for creating new spools, but should be shown in View-Dialog
  • version: simply incremented on updates
  • updated: last Update
  • created: record created on
  • originator: could be user, function, print model or other (internal) explanatory short text

• Journal/History tables are missing some of the before mentioned as they are only being created (and deleted when the master records goes away) Olli: Unclear

  • no version
  • no updated

• Fields which could be easily computed are not meant for storage (like f.e. percent values)

• Note especially for the external tables as they could be extended:

  • talk to development before implementing ;)
  • use a prefix to the variable name like own_ (example own_myfield) as the named content could be overwritten in future development **Olli: Who do mean? From my perpective the "spo_tabels" were tottaly controlled by the plugin, additional columns were "enemies" **
  • be careful with foreign keys as they could break things

---

TODO @Olli: Diagramm communication between PJH and SpoolManager