|Failure create-and-extend-tables, foreign key creation, postgreSQL [message #1801022]
||Fri, 11 January 2019 09:46
| Andreas B
Registered: January 2019
I'm using eclipselink as my JPA provider. I use the property eclipselink.ddl-generation with the value create-or-extend-tables together with a postgreSQL database. Whenever my database did not contain any table, everything is fine and the tables are created as expected. But, if the tables are already existing within my postgreSQL database, a failure message "Constraint FK already exists" will thrown.
The FK is already existing, that is true but this is not a failure message for me. It sounds more or less as an warning message. I changed the logging level eclipselink.logging.level.sql to different states without any changes.
For my local environment I can ignore this failure message. But I using a payara-micro server and try to start my payara instance within an open-shift private cloud. Whenever I start my container, the container start fails related to the eclipselink failure message.
I using the latest eclipse link version 2.7.3.v20180807-4be1041. Within my database (postgreSQL) all permissions are set to the related database user.
I there any additional configuration required to avoid this failure / eclipse link behaviour (create FK relation only if not already existing)? Is there any opportunity to avoid the output of this specific failure?
Powered by FUDForum
. Page generated in 0.01567 seconds