Problem: At this point, the DativeBase backend can read from a legacy MySQL OLD. However, we want DativeBase to be able to import a legacy OLD into a new schema, one which DativeBase can read and write, one implemented in PostgreSQL.
A/C:
- Ensure that DativeBase has a full PostgreSQL schema that can hold an entire legacy OLD. At this stage, we can pretty much copy the legacy OLD MySQL schema to PostgreSQL. However, some things will need to change, notably the weird formbackups table of the legacy OLD will no longer be necessary, given that DativeBase's design is non-lossy from the ground up.
- Create a
sync-old function in DativeBase that can be called from a REPL. It should do the following.
- It takes the name of an existing and locally accessible MySQL OLD (database) name as input.
- It creates a new PostgreSQL OLD in the DativeBase
olds table, naming it the same name as the legacy OLD name. It deletes an existing PG OLD of the same name, or aborts the sync, according to the options supplied by the caller.
- It reads the legacy OLD data and translates it to the new PG OLD schema and writes all data to the new PG OLD tables.
Problem: At this point, the DativeBase backend can read from a legacy MySQL OLD. However, we want DativeBase to be able to import a legacy OLD into a new schema, one which DativeBase can read and write, one implemented in PostgreSQL.
A/C:
sync-oldfunction in DativeBase that can be called from a REPL. It should do the following.oldstable, naming it the same name as the legacy OLD name. It deletes an existing PG OLD of the same name, or aborts the sync, according to the options supplied by the caller.