playframework / playframework/play1
hibernate.id.new_generator_mappings=false in a multidatabase configuration
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.6k
- Forks
- 671
- Avg merge
- 12d 15h
- Merged PRs (30d)
- 1
Description
Hi,
Any idea of how to configure hibernate.id.new_generator_mappings=false in multi database environment ?
hibernate.id.new_generator_mappings=false is working well for the primary database, but it not working for others databases configured in my project
Ps I have tried :
db.database2.hibernate.id.new_generator_mappings=false
database2.hibernate.id.new_generator_mappings=false
...
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
No files, tests, or entry points are named. Start by locating the multi-database configuration and where hibernate.id.new_generator_mappings is applied, then compare the primary and secondary database settings. Done means the setting is honored consistently for the additional databases and the behavior is covered by a reproducible check.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- database
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100