Hello there,
I've encountered InternalException from ObjectDB.
Attached the stacktrace below.
I would require your assistance and advise on resolving this issue.
Likewise, I would provide any information that you require.
Thank you.
Type: Bug Reoprt | Version: 2.3.7 | Priority: Normal | Status: Closed | Replies: 2 |
Hello there,
I've encountered InternalException from ObjectDB.
Attached the stacktrace below.
I would require your assistance and advise on resolving this issue.
Likewise, I would provide any information that you require.
Thank you.
The stack trace indicates an unexpected primary key value during persist.
Please provide more information on the object that fails to persist. Has it class been changed recently? How exactly the primary key is defined? Which value is used as a primary key in the specific object that fails to persist?
Hi there,
I traced the problem to a NullPointerException thrown from inside one entity override of toString() method.
The entity was invoking a method from a null field which is now fixed.
I suppose that ObjectDB could not have known first-hand if a field is null when toString() is invoked. Thus it is the responsibility of developers to avoid NPEs during JPA Entity development.
Thank you.
NOTE: You may mark this issue as [Closed] if you deem this issue as trivial and something developers should take into consideration.