Database migration strategy: need tools for database migrations for Magma. about magma HOT 4 CLOSED

I think more specifically we need to find where in the project the sql tables are initialized, since we need a new column.

edit:
We then need to introduce some logic to create new verification tokens for when old users login.

from magma.

There will be table modifications for the migration strategy; a different table configuration while the server is in that mode of accepting legacy logins, converting them to stacie auth and storing the stacie related item(s?). Then another table modification in a future configuration where there isn't the cruft left over from the migration process (the old login credentials). So, the tables and the data contained within will go through more than a single change. Which was why I added this issue. There may be a larger need for scripts to assist with the migration(s). Maybe there's no need to write a script for this. This item is here in case we need to consider adding a script.

from magma.

schema.init is the script that currently initializes all the required tables.

It calls multiple *.sql files that exist in the project. Ladar recommended MySQL workbench, downloadable from mysql.com to as a gui tool for schema editing.

from magma.

Zach updated schema.init, added columns to the user-table db as needed to integrate Ivan's STACIE updated. The immediate need that this issue was related to is resolved. Issues remain that are related to migration strategy but it's unclear how those issues might drive more updates to the sql tables for now. Open new issues as they become issues after defining a course for migration.

from magma.