-
-
Notifications
You must be signed in to change notification settings - Fork 93
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
Marks failed migrations as completed #72
Comments
Could you try this with the latest version |
I think I was getting #68 with the latest, but I'll check again and report. |
Yeah, HugSQL got updated to support the changes in clojure.java.jdbc, so latest versions should work. |
Just checked on 0.8.22, I'm still getting |
The problem is that clojure.java.jdbc API changed in version 0.6.x, so any code using the old API is incompatible with it. So it sounds like you have some code that depends on the older API or there's a bug in migratus where it's trying to call the old API still. If you could paste the new stack trace, I can help narrow this down. |
I'm using |
Ok, found it. |
There is PR for this: korma/Korma#358 (which doesn't help me right now but yeah...) |
No worries, I think using an older version of migratus would be the way to go until Korma updates to use the new API. |
Yeah, or one more reason to migrate to HugSQL :P |
Yeah it's very nice, I've migrated all my projects over at this point and very happy with it. :) |
I thought about migrating gradually, but it seems HugSQL's and Korma's |
I don't think the api changed much between 0.3.7 and 0.4.x, so you might be able to get away with a fairly recent version of HugSQL. |
FWIW, I've been able to get both HugSQL and Korma to coexist in harmony by using these dependencies:
|
@timgilbert awesome, thanks a lot! |
I just experienced this: https://gist.github.com/sickill/d5468aa92a0c390bfe39f193d44f1295
You can see it failed to apply both migrations from the file, yet it still marked it as complete, and I can't rollback now (need to manually delete from schema_migrations).
Using migratus 0.8.13 and org.postgresql/postgresql "9.4-1201-jdbc41".
The text was updated successfully, but these errors were encountered: