Community
Participate
Working Groups
Since we turn off native SQL queries once we discover at least one multitenant entity, DDL generation will fail (exception thrown) Caused by: Exception [EclipseLink-6175] (Eclipse Persistence Services - 2.4.0.v20110824-r9956): org.eclipse.persistence.exceptions.QueryException Exception Description: Native SQL queries have been disabled. This is done either by setting the persistence unit property eclipselink.jdbc.allow-native-sql-queries to false or having at least one multitenant entity defined in your persistence unit. Check your persistence unit specification. To allow native sql queries, set this property to true. Alternatively, individual queries may bypass this setting by setting the eclipselink.jdbc.allow-native-sql-query query hint to true. Query: DataModifyQuery(sql="DROP TABLE B") DDL generation queries should bypass the global setting and allow for native sql queries.
Created attachment 203290 [details] Proposed changes (2.3.1 stream)
Created attachment 203339 [details] Updated patch for 2.3.1 stream
Created attachment 203342 [details] Patch for trunk
Changes have been submitted. Verified by: Gordon Yorke Tests: Opened up the DDL generation model which has multitenant entities and previously set the allow native SQL queries on the PU. With these changes, that flag is no longer needed in this case.
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink
