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

Doc: Don't mix up native schema creation with JPA 2.1 standard one [SPR-13040] #17632

Closed
spring-projects-issues opened this issue May 18, 2015 · 1 comment
Assignees
Milestone

Comments

@spring-projects-issues
Copy link
Collaborator

@spring-projects-issues spring-projects-issues commented May 18, 2015

Oliver Drotbohm opened SPR-13040 and commented

JPA 2.1 defines a property to enable schema creation with a persistence provider. According to Steve Ebersole of Hibernate that might conflict with the native schema creation we currently activate in the JpaVendorAdapter implementations (at least for Hibernate). We should make sure that a user does not accidentally activates both.


Referenced from: commits 11ec999

@spring-projects-issues
Copy link
Collaborator Author

@spring-projects-issues spring-projects-issues commented May 18, 2015

Juergen Hoeller commented

I'm afraid we have no good way to check for such configuration overlap: A JpaVendorAdapter implementation doesn't have access to the overall JPA configuration, and in the EntityManagerFactoryBean itself, a Hibernate specific check would be a hack.

For that reason, I'd suggest to add a note on this to the reference documentation instead.

Juergen

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants