openjpa-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From andyatmiami <>
Subject dropDB SQL generation doesn't seem to account for foreign keys
Date Fri, 13 Jul 2012 13:49:49 GMT
I want to issue a dropDB to clear out my existing database objects - but it
does not seem to account for Foreign Key constraints.  The drop statements
(which I am outputting to a sql file) seem to simply appear in alphabetical
order and once I try to execute the sql file, I get the following error: 

Cannot delete or update a parent row: a foreign key constraint fails 

Is there a way to drop all my tables if I am using foreign keys? I specify
these foreign keys through JPA Annotations - I am working on a "net new" DB
so there is no concern over existing Foreign Keys managed outside of my
code.  Thanks in advance. 


Relevant pom config: 


View this message in context:
Sent from the OpenJPA Users mailing list archive at

View raw message