[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[eclipselink-users] Zero not a valid PK value?
|
I filed a bug about this - #240153 -
https://bugs.eclipse.org/bugs/show_bug.cgi?id=240153
Anyway, this didn't start to happen since M10, but if you have a
transaction open and select an Entity with a value of zero as it's PK,
you get this when you try to check for changes to the Unit of Work
(and probably on a save), I think it's a bit of a show stopper since
we can't be the only one with a lone zero value in an id field.
Local Exception Stack:
Exception [EclipseLink-7197] (Eclipse Persistence Services - 1.0
(Build SNAPSHOT - 20080625)):
org.eclipse.persistence.exceptions.ValidationException?
Exception Description: Null primary key encountered in unit of work
clone [com.ussignalcom.plugin.om.model.eo.ServiceBandwidths@1854518].
at org.eclipse.persistence.exceptions.ValidationException?.nullPrimaryKeyInUnitOfWorkClone(ValidationException?.java:1294)
at org.eclipse.persistence.descriptors.changetracking.DeferredChangeDetectionPolicy?.calculateChanges(DeferredChangeDetectionPolicy?.java:84)
at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl?.calculateChanges(UnitOfWorkImpl?.java:558)
at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl?.hasChanges(UnitOfWorkImpl?.java:2553)
/Tim
