-
Notifications
You must be signed in to change notification settings - Fork 130
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
Ability to run both SQL and RS migrations #170
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi! And thanks for this amazing work! ❤️ left some comments, if you feel changing the tests structure to address the new changes takes too much time no worries, we can do it in subsequent PR's :)
@@ -0,0 +1,2 @@ | |||
ALTER TABLE cars |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is the addition of this sql migration on the mod migrations dir on purpose? i.e. to test a dir with both sql and mod migrations, I think since we are now merging the macro do embed migrations it probably makes sense to change the tests to work with both, what do you think?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I did it on purpose, to test both sql and mod. Also agree tests need a revisit!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok yeah so since the tests are passing and work, we can do it on a subsequent PR if you feel like doing it, and we can merge this one before
@@ -18,41 +16,46 @@ mod mysql { | |||
|
|||
mod embedded { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
embedded used to be the .sql
migrations but since now everything is embedded this relates with my question above that it probably makes sense to update the tests
Thanks. I agree. There are several tests to test SQL and RS. I'm sure we can merge (remove) some of them. It was hard for me to do this, since I'm kinda new to the source code. |
The issue in GH Actions is related to another package. |
it was needed because of |
@jxs thanks. Checked that. It's not needed to be on nightly anymore. So removed it in this PR. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM now! thanks!! 🎆
@jxs I don't like what I have done here :( “Migration” can be anything, not even SQL. For example, I may want to use refinery to copy files from s3 to blob storage! Any idea how can we solve it? (I'm trying myself to solve it, may come back with some ideas :/ ) |
Hi, wdym debug? I can understand the auto-completion issues, but those are tooling related. If there's a way to improve them i am all for that, but I don't think that it should block these changes
yeah, but that also happened with mod migrations, you can do whatever you want inside the
I can also think about an idea to make it so that when you edit these files |
By debug I mean, to be able to find the problems in the code while writing it. Before running migration.
Yes, but in this case, I need to define s3 and blob storage requirements in Cargo.toml.
That would be awesome. |
but how is this different from previous
and the compiler/clippy complains about that? |
Oh, it isn't? So I'm fine with this PR then :) Seems like another topic then
I still don't know. Shouldn't be the case. |
I don't know ehe, so far the only downside from introducing this PR seems to be that auto-completion no longer works on the migration files right? Tbh I think that's a minor issue, which can be addressed later
aha then it isn't a problem right? |
OK, so all good 👍🏼 |
and use it on `find_migration_files` to fix the bug introduced on rust-db#170 where refinery_cli tries to embed all kinds of files not only .sql
and use it on `find_migration_files` to fix the bug introduced on rust-db#170 where refinery_cli tries to embed all kinds of files not only .sql
and use it on `find_migration_files` to fix the bug introduced on rust-db#170 where refinery_cli tries to embed all kinds of files not only .sql
and use it on `find_migration_files` to fix the bug introduced on rust-db#170 where refinery_cli tries to embed all kinds of files not only .sql
and use it on `find_migration_files` to fix the bug introduced on rust-db#170 where refinery_cli tries to embed all kinds of files not only .sql
and use it on `find_migration_files` to fix the bug introduced on rust-db#170 where refinery_cli tries to embed all kinds of files not only .sql
and use it on `find_migration_files` to fix the bug introduced on rust-db#170 where refinery_cli tries to embed all kinds of files not only .sql
and use it on `find_migration_files` to fix the bug introduced on rust-db#170 where refinery_cli tries to embed all kinds of files not only .sql
* refinery_cli: re-introduce MigrationType: and use it on `find_migration_files` to fix the bug introduced on #170 where refinery_cli tries to embed all kinds of files not only .sql * tests: update test suite to match new merged macros: remove redundant tests, closes #171 * ci: update rust stable version * ci: use github barrel fork to address TLS issues, while a proper version with SqlServer support isn't released
Hey! I am using refinery and just found out, that this PR is not yet in some publicly released crates.io version. @jxs are you planning to release that soon or is it possible to directly depend on the github crate? |
Hi! Yeah I'll try to cut a release today with all the new changes :) |
0.7.0 released :) |
@jxs awesome, thank you so much for all your work! |
Fixes #154