-
Notifications
You must be signed in to change notification settings - Fork 22
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
SqlMigrations don't work with slick-migration-api-flyway #98
Comments
What do you recommend? |
Well... if you could just override |
Right, I mean what do you suggest it be overridden to?
…On Thu, Dec 3, 2020, 6:05 AM Paweł Lipski ***@***.***> wrote:
Well... if you could just override toString in trait SqlMigration :)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#98 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAYAUE25E5YQN7MITYBKP3SS5WGTANCNFSM4R4WMBBA>
.
|
Hmmm same as in my implementation?... Possibly with |
Could you send a PR? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Since the result of
slick.migration.api.SqlMigration.apply
doesn't overridetoString
, the generateddescription
of aSqlMigration
looks likeSqlMigration$$anon$1@5becf99e
, and is a different string each time a new object is created (incl. when a new JVM is launched).This leads to Flyway failing with ``Migration description mismatch for migration version ...`.
As a workaround, once could do sth like:
The text was updated successfully, but these errors were encountered: