Re: [eclipselink-users] NPE when updating entity where only @Element-col

[Gary Roach <gary719_list1@xxxxxxxxxxx>]

On 05/03/2016 03:40 PM, Andreas Joseph Krogh wrote:

På tirsdag 03. mai 2016 kl. 09:08:54, skrev Mauro Molinari <mauromol@xxxxxxxxxx>:

I have no idea (I'm just an EclipseLink user like you and never used it with PostgreSQL), but... what if you compare the same buildCallWithReturning implementation on another SQLPlatform (MySQL or such)? Would it throw NPE as well if sqlCall is null?
You may understand if the problem is in the PostgreSQLPlatform or in the fact that sqlCall is null...

 

The problem I'm facing is that buildCallWithoutReturning(session) retursn null, so I'm not really interested in what other platforms do when null is returned.

 

The strange thing is that this only happens when i retrieve an entity with LockModeType.PESSIMISTIC_WRITE, retrieving it using regular find() works ok.

This is related to my other thread "Property-change event fails because of IndirectSet.attributeName is null".

 

--

Andreas Joseph Krogh

CTO / Partner - Visena AS

Mobile: +47 909 56 963

andreas@xxxxxxxxxx

www.visena.com

 

_______________________________________________
eclipselink-users mailing list
eclipselink-users@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/eclipselink-users

Andreas

Postgresql is not a problem. Dango (pydev) has its own internal database engine that can be used for development work. I never got that far with my setup before conflicts started.

Gary R.