You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Do I understand correctly, that you want to have something like this:
1_create_table_a.cql
2_create_table_b.cql
1.1_add_column_to_table_a.cql
I honestly think that this would result in a very high overhead and would make things very complicated as you would be required to maintain a version per table. What is done currently is that you check the schema_migration table for the latest version and then see which higher versions are provided in the script source, which is fairly simple.
If however we go for one 'version scope' per table the tool would be required to check for every major version if there are new minor versions.
If you really need this, you could achieve this also by using the code of this pull request. I see that I will release this soon.
You could basically create one instance per table and just provide different folders as source for the migrations. You just need to provide one prefix per table and you would maintain all tables in separate schema migration tables.
is it possible to support the script version in format like 1.1,1.2?
so we can create separate cql file for each table.
The text was updated successfully, but these errors were encountered: