playframework / playframework/play1
hibernate_sequence doesnt exists.
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.6k
- Forks
- 671
- Avg merge
- 12d 15h
- Merged PRs (30d)
- 1
Description
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the upgrade to Play 1.7.1 on macOS with MySQL and the reported insert operation. Trace startup and schema or sequence handling to find why hibernate_sequence is required instead of the existing auto_increment column. Done means inserts work without the missing-table exception and a regression test covers the case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, mysql
- Domain
- backend, database
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100