I've found another issue with 4.1.M1 through my unit tests. If you have:
1) modeled a primary key as an ObjAttribute, like customerPK
2) modeled it as an object type, like java.lang.Long
3) are using the Cayenne-Generated (Default) PK generation strategy
Then Cayenne won't generate any PKs for t
Hi John,
I've noticed this too, maybe we should change cgen templates to use
Object type exactly as set in the model. After all it is confusing by
itself regardless problem you mentioned.
As for treating zero as missing PK, this can be harder as logic around
there looks fragile to me.
On Fri, Nov
Yeah, right now the template is trying to be smarter than the developer by
using primitives where it should be ok. But there are problems with this
besides the above problem due to backwards compatibility. And it is also
surprising for the developer. So I think sticking to the type as entered
in
