JPA 2.1 Schema generation property drop-and-create does not drop
Description
Activity
Christian Beikov January 21, 2025 at 1:07 PM
Probably was fixed via https://hibernate.atlassian.net/browse/HHH-10458#icft=HHH-10458
Steve Ebersole October 28, 2015 at 3:25 AM
As part of verifying that this issue affects 5.0, please just set the "Affects version". Leave the "verify-affects-5.0" label and leave the issue in "Awaiting Response" status; these are critical for us to be able to track these verifications and triage them. Thanks.
Steve Ebersole October 27, 2015 at 7:15 PM
This bug report does not indicate that the reported issue affects version 5.x. Versions prior to 5.x are no longer maintained. It would be a great help to the Hibernate team and community for someone to verify that the reported issue still affects version 5.x. If so, please add the 5.x version that you verified with to the list of affected-versions and attach the (preferably SSCCE) test case you used to do the verification to the report; from there the issues will be looked at during our triage meetings.
For details, see http://in.relation.to/2015/10/27/great-jira-cleanup-2015/
Details
Details
Assignee
Reporter
Labels
Original estimate
Time tracking
Affects versions
Priority
Critical
I am using the new JPA 2.1 property "javax.persistence.schema-generation.database.action" with the value "drop-and-create". Hibernate generate the table-statements but does not drop the tables first. This makes my integration tests with Arquillian who do multiple consecutive deploys not work.
I have tried both the ExampleDS datasource in WildFly that use an in-memory H2 database and my own datasource that connects to a networked MySQL server.