[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [eclipselink-users] LEFT OUTER JOIN not being honored
|
I actually had not specified the target database, which defaults EclipseLink to "Auto" and should allow EclipseLink to retrieve the database type for the JDBC MetaData. Looking at the log file pertaining to when my application starts, I see the following:
[#|2009-05-04T11:00:42.315-0700|CONFIG|sun-appserver2.1|org.eclipse.persistence.session.file:/D:/dev/glassfish-v2.1/domains/domain1/applications/j2ee-apps/ecv/ecv-ejb_jar/-ecv-pu.connection|_ThreadID=45;_ThreadName=Thread-1010;|Connected: jdbc:derby://cmathrusxp:1527/ecv;;create=true
User: ecv
Database: Apache Derby Version: 10.4.2.1 - (706043)
Driver: Apache Derby Network Client JDBC Driver Version: 10.4.2.1 - (706043)|#]
[#|2009-05-04T11:00:42.315-0700|CONFIG|sun-appserver2.1|org.eclipse.persistence.session.file:/D:/dev/glassfish-v2.1/domains/domain1/applications/j2ee-apps/ecv/ecv-ejb_jar/-ecv-pu.connection|_ThreadID=45;_ThreadName=Thread-1010;|connecting(DatabaseLogin(
platform=>JavaDBPlatform
user name=> ""
connector=>JNDIConnector datasource name=>null
))|#]
Even though this shows the target database to be Derby, I explicitly set the database
property name="eclipselink.target-database" value="JavaDB" but the generated SQL still showed the issue.
SELECT t0.id, t0.mod_date, t0.create_date, t0.version, t0.sieve, t0.mod_by, t0.resource_id, t0.severity, t0.distribution_id
FROM notification_definition t0 LEFT OUTER JOIN distribution_sieve t1 ON (t1.id = t0.sieve)
WHERE ((((t0.resource_id = ?) AND (t0.severity IS NULL)) OR ((t0.resource_id IS NULL) AND (t0.severity = ?)))
AND ((((t1.include = 1) AND (t1.organization = ?)) OR ((t1.include = 0) AND NOT ((t1.organization = ?)))) OR t0.sieve =* NULL))
Thanks for the help...
View this message in context:
Re: LEFT OUTER JOIN not being honored
Sent from the
EclipseLink - Users mailing list archive at Nabble.com.
