-
Notifications
You must be signed in to change notification settings - Fork 683
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
hibernate_sequence doesnt exists. #1454
Comments
@samlotti check out these previous issues that I think might be related. They suggest setting |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Are you looking for help?
This is an issue tracker, used to manage and track the development of Play. It is not a support system and so it is not a place to ask questions or get help. If you're not sure if you have found a bug, or if you have a feature request, the best place to start is with either the Discuss Play Forum or Stack Overflow.
Play Version (1.5.x / etc)
Version 1.7.1
Operating System (Ubuntu 15.10 / MacOS 10.10 / Windows 10)
Mac os
Ventura 13.6 (22G120)
Paste the output from
java -version
at the command line.OpenJDK Runtime Environment Corretto-11.0.20.9.1 (build 11.0.20.1+9-LTS)
Library Dependencies
mysql Ver 14.14 Distrib 5.5.27, for osx10.6 (i386) using readline 5.1
Expected Behavior
Expect to be able to insert a row into the database. the sequence generator
Mysql should use the auto_increment column to get the next sequence value,
Actual Behavior
Get exception:
Table 'ct20170902.hibernate_sequence' doesn't exist
Please provide a description of what actually happens, working from the same starting point.
Upgrading from an old version of play, to play 1.7.1, trying to start the server and get the exception saying the sequence doesn't exists. This has been working and using the auto-increment column.
Reproducible Test Case
Please provide a PR with a failing test.
If the issue is more complex or requires configuration, please provide a link to a project on Github that reproduces the issue.
The text was updated successfully, but these errors were encountered: