-
-
Notifications
You must be signed in to change notification settings - Fork 282
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
Play evolutions throwing error when trying to run it for the first time #600
Comments
This is the configuration that I am using,
and this is the build.sbt
|
I have also experienced this error and this was my resolution: https://stackoverflow.com/questions/59701024/cannot-create-play-evolutions-table A basic config to postgres and like the stackoverflow user, changing from 2 threads to 10 threads cleared the issue. |
Not sure what the original problem really is about, but just guessing, could it be that a play-slick component needs to depend on (inject) the |
I had a look and think having play-slick/src/core/src/main/scala/play/api/db/slick/SlickApi.scala Lines 40 to 44 in abe0d9a
|
for me, the workaround of changing the number of threads did not work. |
so I guess to try this I would have to build play framework myself? |
@nemoo No not Play, but "only" play-slick. Just check out the repo, apply the fix and run |
edit: got it to compile (without the new injection) by adding,
now off to testing ok I might need some help with that.
When starting play, I now get those version conflicts below. How would I tackle those?
|
Ok I am struggling to import ApplicationEnvolutions in the play-slick SlickApi.scala File. I tried it with: which gives me:
play slick core Dependencies do not include play-jdbc-evolutions, therefore ApplicationEvolutions is not visible: |
Update: When I try to use this build in my play app, I now get this error:
|
Error:
[PSQLException: ERROR: relation "play_evolutions" does not exist Position: 8]
.I can see the table
play_evolutions
in the db. Play does create this table on starting the server.The text was updated successfully, but these errors were encountered: