Create new tables user2, organisation2 and purge the old ones. Store the relationship data
in either users2 or organisation2 table as array or jsonb or a combination of both.
Once the migration is done, write unit tests for the places where users and organisation tables are queried or used in gkcore
If we don’t support partial imports, we should state it.
If we want to save import stats, we should make a file & save it there.
VK
After the ununique users from users table have renamed their default username, purge that data from the users table. And when users table is empty remove it completely, to avoid data reproduction
Show import summary for each section in json stats
when date sort has no data, show message
rest2e2
Import must also check if any existing data is replaced, i.e opening bal
Import stats can be stored in audit logs
Dhruvin
Experimented Packaging gkapp & gkcore to alpine
We could host a seperate alpine repository for gkcore until we settle with a fixed release