Currently only one "update entry" is created, for example if editing locality and adding species, a locality update entry is written into "now_lau" table. Actually, any new species updates should go to their own update-event. The log-entries for now_ls table should have both ids of luid and suid.
Similarly, if time units (or their bounds) are edited so that it changes a locality's ages, it should create an entry to now_lau also. (related to next task:)
[ ] If time units or time bounds are changed and those are used in any localities, those localities age calculations have to be re-done and re-written in the db, and locality update events must be created for those.
[ ] Put env variables that tell what version of database we are running
[x] disable all edit routes and visibility of edit buttons in frontend if using real database
[ ] Remove staging-mode from the types of edit that do not need update-entries
[x] Add button to access the new-creation mode
[ ] Fix pk_data column of log-table
[ ] Create a separate function for using the write operation without the update/logging feature, so it can be used for references, people, etc.
[x] Clean up code
[ ] Create testing system and cleaner debug logs
[x] Make db-names configurable by env variables
[x] Merge the first version to main
[ ] When time unit's bounds change these must change in each locality
[ ] After creating a new item, user should be redirected to it
[ ] If nothing was written, don't create an update entry (possibly run diff in frontend already before entering staging, and inform user there are no changes. But backend should also check)
[ ] Delete operation
[ ] User rights: Find out how reference rights should be handled and if all "no", "pl" and "plp" are deprecated
Currently only one "update entry" is created, for example if editing locality and adding species, a locality update entry is written into "now_lau" table. Actually, any new species updates should go to their own update-event. The log-entries for now_ls table should have both ids of luid and suid.
Similarly, if time units (or their bounds) are edited so that it changes a locality's ages, it should create an entry to now_lau also. (related to next task:)
[ ] If time units or time bounds are changed and those are used in any localities, those localities age calculations have to be re-done and re-written in the db, and locality update events must be created for those.
[ ] Put env variables that tell what version of database we are running
[x] disable all edit routes and visibility of edit buttons in frontend if using real database
[ ] Remove staging-mode from the types of edit that do not need update-entries
[x] Add button to access the new-creation mode
[ ] Fix
pk_datacolumn of log-table[ ] Create a separate function for using the write operation without the update/logging feature, so it can be used for references, people, etc.
[x] Clean up code
[ ] Create testing system and cleaner debug logs
[x] Make db-names configurable by env variables
[x] Merge the first version to main
[ ] When time unit's bounds change these must change in each locality
[ ] After creating a new item, user should be redirected to it
[ ] If nothing was written, don't create an update entry (possibly run diff in frontend already before entering staging, and inform user there are no changes. But backend should also check)
[ ] Delete operation
[ ] User rights: Find out how reference rights should be handled and if all "no", "pl" and "plp" are deprecated