Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support script version in fromat of 1.1,1.2 #32

Open
pura1029 opened this issue Jan 29, 2019 · 2 comments
Open

Support script version in fromat of 1.1,1.2 #32

pura1029 opened this issue Jan 29, 2019 · 2 comments

Comments

@pura1029
Copy link

pura1029 commented Jan 29, 2019

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.

@patka
Copy link
Owner

patka commented Feb 13, 2019

Hi,

sorry for the late response.

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.

Cheers
Patrick

@pura1029
Copy link
Author

How i will configure in spring?
There is no option to configure one prefix per table.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants