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

update and/or validate javax.persistence.schema-generation.database.action #68

Closed
lukasj opened this issue Nov 12, 2013 · 4 comments · Fixed by #431
Closed

update and/or validate javax.persistence.schema-generation.database.action #68

lukasj opened this issue Nov 12, 2013 · 4 comments · Fixed by #431

Comments

@lukasj
Copy link
Contributor

lukasj commented Nov 12, 2013

I think that an "update" and a "validate" schema-generation.database.action might come in handy, especially for production environments where Java EE 7 will be running in the comming future.

Of course you don't want your database to be accidentally being removed if you still have the "create-drop" enabled, and a new action won't solve that.
But without the "update" action you still have to resort to solutions like Google Flyway or DbMaintain to update an existing database schema.

Are there plans to incorporate a new action like "update" or "validate", the way Hibernate supports it?
Or are they left out by design?

@lukasj
Copy link
Contributor Author

lukasj commented Nov 12, 2013

@glassfishrobot Commented
Reported by steveschols

@lukasj
Copy link
Contributor Author

lukasj commented May 5, 2017

@glassfishrobot Commented
This issue was imported from java.net JIRA JPA_SPEC-68

@lukasj
Copy link
Contributor Author

lukasj commented Aug 31, 2018

@gavinking
Copy link
Contributor

We will probably add a validate setting as part of the work on #399. We probably won't add update, since it's just never very robust.

@gavinking gavinking linked a pull request Aug 12, 2023 that will close this issue
@lukasj lukasj added this to To do in 3.2.0 via automation Aug 21, 2023
@lukasj lukasj moved this from To do to Done in 3.2.0 Aug 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
3.2.0
Done
Development

Successfully merging a pull request may close this issue.

2 participants