Open isedwards opened 8 years ago
It is required that before the user starts data migration the following has to be in place:
- Climsoft V4 and MariaDB installed
- Scripts for creating Climsoft database that comes with the Setup have been executed and confirmed that mariadb_climsoft_db_v4 schema exists in MariaDB
- A copy of Climsoft 3.2 backup file in text csv file has been made or mysql_climsoft_db_v3 schema with data exists
Migration is supposed to append data to any existing one and it can be done incrementally. So a massage on presence of some data may not be necessary
The location of the Climsoft V3 backup file is the choice of the user. It will be browsed for when migrating process is run
The new Data Migration form (to migrate data from Climsoft version 3.2 databases to version 4) is working, but it requires the user to have first created an empty Climsoft v4 schema to load data into.
e.g. the destination database name that the user provides must exist on the server that Climsoft is currently connected to, and must have empty tables with the correct columns to receive the data.
The screenshot below shows the outcome of providing the name of an new empty database that does not yet have any of the required tables (e.g. there is no
observationinitial
table).Updates:
V4 db
field?C:\Users\guest_user\Documents\GitHubVisualStudio\Climsoft\ClimsoftVer4\ClimsoftVer4\bin\Debug\data\backup.csv
can not be created. By default MySQL and MariaDB are only able to write output files to particular locations for security, e.g.C:\Program Files\MariaDB 10.1\data
.