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

Add support for JPA 2.1 schema generation options in AbstractJpaVendorAdapter [SPR-10832] #15458

Closed
spring-issuemaster opened this issue Aug 13, 2013 · 3 comments

Comments

@spring-issuemaster
Copy link
Collaborator

@spring-issuemaster spring-issuemaster commented Aug 13, 2013

Adam Walczak - WALCZAK.IT opened SPR-10832 and commented

A nice summary of the can be found here:
https://blogs.oracle.com/arungupta/entry/jpa_2_1_schema_generation


No further details from SPR-10832

@spring-issuemaster

This comment has been minimized.

Copy link
Collaborator Author

@spring-issuemaster spring-issuemaster commented Aug 13, 2013

Adam Walczak - WALCZAK.IT commented

if accepted this improvement should deprecate the generateDdl property which is confusing (#11502) and gives no information which strategy will be used (update, create, drop-create; create script or work on database)

@spring-issuemaster

This comment has been minimized.

Copy link
Collaborator Author

@spring-issuemaster spring-issuemaster commented Sep 25, 2013

Juergen Hoeller commented

Why not simply set the corresponding JPA properties? It's not immediately obvious to me what major convenience a JpaVendorAdapter could add here.

Juergen

@spring-issuemaster

This comment has been minimized.

Copy link
Collaborator Author

@spring-issuemaster spring-issuemaster commented Jan 12, 2019

Bulk closing outdated, unresolved issues. Please, reopen if still relevant.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.