There seems to a minor confusion in the 1.2.1 OpenJPA manual regarding
openjpa.jdbc.MappingDefaults
Section 7.4 Reference Guide - I discovered by trial and error that the
"jpa" alias is the default and the "default" alias is NOT the default.
Using the "jpa" alias generates the same forward ma
After restarting my server, this issue has disappeared, so please don't reply to
my previous message unless I can reproduce that again. Thanks
Adam Hardy on 04/04/09 12:39, wrote:
Hi Michael,
I just re-read your message and saw the misunderstanding:
OpenJPA is not persisting null as you had
Hi Michael,
I just re-read your message and saw the misunderstanding:
OpenJPA is not persisting null as you had thought, it is changing the null value
to an empty string.
I also realised I wrote some logic into the enum which might be causing the
problem, since I stripped the logic out and i
I followed your suggestion and placed the 'nullable' attribute on the column,
but it had no impact.
I'm having problems grasping the logic behind that nullable attribute.
If the column is not nullable and I also configure JPA with nullable=false, then
surely OpenJPA should throw an exception b
