...
will need to be migrated to PostgreSQL?
testing - PostgesSQL uses low isolation level by default - might solve the problem
might not be needed, documentation on how to approach potential problems
wip
Legacy Offline Mode
Impact: none
doesn't work in legacy version, not used
needs popping up but will have to be addressed as new features
...
Impact:
new installations (new, empty DB) not yet using all attributes
migration script need to know DB version to adjust to all scenarios
Discussion:
done - DB - initialisation:
two separate INIT scripts for PostgreSQL & MS SQL available
done - legacy migration:
migration script for the legacy data available
done - future development will be against PostgreSQL
other DB will have to use Django Migration scripts to fork to their DB system (automatically through Django “make migration“ - might need manual adaptations)
documentation needed
most is done automatically at startup
create a link in each release note point at a migration path for that version with manual exceptions
testing of the documentation is needed
Reports
List of reports: Report module
wip - which reports still need to be migrated? which ones are still used?
some reports don’t work
list of reports to all sites with feedback on what they are still using (no nice-to-haves!)
also have a look at https://www.metabase.com/start/oss/
Documentation How-To / Best-Practices of Migration
...