Skip to content
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

HibernateJpaVendorAdapter sets hibernate.hbm2ddl.auto to "update" [SPR-6836] #11502

Closed
spring-projects-issues opened this issue Feb 14, 2010 · 3 comments
Assignees
Labels
in: core status: declined type: enhancement

Comments

@spring-projects-issues
Copy link
Collaborator

@spring-projects-issues spring-projects-issues commented Feb 14, 2010

Ivan Balashov opened SPR-6836 and commented

When HibernateJpaVendorAdapter is configured with generateDdl="true" the value of hibernate.hbm2ddl.auto is set to "update", overriding actual value specified in persistence.xml.


Affects: 2.5.6

@spring-projects-issues
Copy link
Collaborator Author

@spring-projects-issues spring-projects-issues commented Feb 14, 2010

Juergen Hoeller commented

Well, that's the point of the "generateDdl" flag: It will set the corresponding property of the underlying persistence provider. If you'd rather configure those properties natively (e.g. in persistence.xml), then simply don't bother with setting "generateDdl" on the JpaVendorAdapter...

Juergen

@spring-projects-issues
Copy link
Collaborator Author

@spring-projects-issues spring-projects-issues commented Feb 14, 2010

Ivan Balashov commented

This flag is rather misleading for Hibernate, which beside "update" also has "create" and "create-drop" options.

To enable "create", generateDdl should be set to "false", which at the first sight doesn't make any sense.

@spring-projects-issues
Copy link
Collaborator Author

@spring-projects-issues spring-projects-issues commented Jun 18, 2012

Rossen Stoyanchev commented

This issue has been resolved through a selective bulk update, as part of a larger effort to better manage unresolved issues. To qualify for the update, the issue was either created before Spring 3.0 or affects a version older than Spring 3.0 and is not a bug.

There is a good chance the request was made obsolete, or at least partly outdated, by changes in later versions of Spring including deprecations. It is also possible it didn't get enough traction or we didn't have enough time to address it. One way or another, we didn't get to it.

If you believe the issue, or some aspects of it, are still relevant and worth pursuing at present you may re-open this issue or create a new one with a more up-to-date description.

We thank you for your contributions and encourage you to become familiar with the current process of managing Spring Framework JIRA issues that has been in use for over a year.

@spring-projects-issues spring-projects-issues added status: declined type: enhancement in: core labels Jan 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: core status: declined type: enhancement
Projects
None yet
Development

No branches or pull requests

2 participants