fabianlindfors 7c48974308 Use separate table for completed migrations ... Before, the entire state was stored as a JSON encoded blob including all completed migrations. This commits moves the migrations into a dedicated table, which prevents the encoded from growing indefinitely. The size of the state probably wouldn't have become a problem but it feels weird for a schema migration tool to not use a proper schema. Next, the version stored in the state struct will be moved to a separate key in the `reshape.data` table and `State` will become an enum with the same structure as `Status`. The naming right now is a bit confusing.		2022-01-13 23:46:07 +01:00
..
add_column.rs	Use separate table for completed migrations	2022-01-13 23:46:07 +01:00
add_index.rs	Add builder for create_table migration	2022-01-10 21:59:20 +01:00
alter_column.rs	Use separate table for completed migrations	2022-01-13 23:46:07 +01:00
common.rs	Add check for dangling changes at end of tests	2022-01-03 22:09:16 +01:00
create_table.rs	Use separate table for completed migrations	2022-01-13 23:46:07 +01:00
failure.rs	Use separate table for completed migrations	2022-01-13 23:46:07 +01:00
remove_column.rs	Add builder for create_table migration	2022-01-10 21:59:20 +01:00
remove_index.rs	Add remove_index action	2022-01-12 01:12:08 +01:00
remove_table.rs	Add builder for create_table migration	2022-01-10 21:59:20 +01:00
rename_table.rs	Add builder for create_table migration	2022-01-10 21:59:20 +01:00