RE: [eclipselink-users] Logging SQL results

[cowwoc <cowwoc@xxxxxxxxxxxxxxxx>]

Ah! :) Can someone please add this to the documentation?
http://wiki.eclipse.org/EclipseLink/Examples/JPA/Logging doesn't mention
this logging level or what extra it will log.

Thanks,
Gili


Thomas Paradies wrote:
> 
> Gili,
> 
> set eclipselink.logging.level to the finest level (ALL).
> 
> Thomas 
> 
> -----Original Message-----
> From: eclipselink-users-bounces@xxxxxxxxxxx on behalf of cowwoc
> Sent: Mon 9/22/2008 5:52 AM
> To: eclipselink-users@xxxxxxxxxxx
> Subject: Re: [eclipselink-users] Logging SQL results
>  
> 
> I tracked this problem down to a bug in the way warp-persist is handling
> Transaction-per-Request. The same EntityManager was being reused across
> different HTTP requests leading to the following behavior:
> 
> - Request goes to Thread 1. It saves version 10
> - Request goes to Thread 2. It saves version 11.
> - Request goes to Thread 1. The query returns the cached object (version
> 10). When the thread attempts to commit this a OptimisticLockException is
> thrown.
> 
> I'd still to know how to get EclipseLink to log SQL query results
> though...
> 
> Gili
> -- 
> View this message in context:
> http://www.nabble.com/Logging-SQL-results-tp19600126p19601515.html
> Sent from the EclipseLink - Users mailing list archive at Nabble.com.
> 
> _______________________________________________
> eclipselink-users mailing list
> eclipselink-users@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/eclipselink-users
> 
> 
>  
> _______________________________________________
> eclipselink-users mailing list
> eclipselink-users@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/eclipselink-users
> 
> 

-- 
View this message in context: http://www.nabble.com/Logging-SQL-results-tp19600126p19607920.html
Sent from the EclipseLink - Users mailing list archive at Nabble.com.