Sorry this is Cayenne 3.1 API, and there is a typo :)
3.1: Cayenne.intPkForObject
3.0: DataObjectUtils.intPkForObject
On Mar 9, 2012, at 11:33 AM, cghersi wrote:
> Hi Andrus,
>
> I cannot find documentation for your proposal (Cayenne.inPkForObject): may
> you give me an example of use?
>
>
Hi Cristiano,
For Cayenne 3.0, it is in DataObjectUtils.intPKForObject().
mrg
On Fri, Mar 9, 2012 at 11:33 AM, cghersi wrote:
> I cannot find documentation for your proposal (Cayenne.inPkForObject): may
> you give me an example of use?
Hi Andrus,
I cannot find documentation for your proposal (Cayenne.inPkForObject): may you
give me an example of use?
Thank you very much.
Best
cghersi
From: Andrus Adamchik [via Cayenne]
[mailto:ml-node+s195n3812833...@n3.nabble.com]
Sent: venerdì 9 marzo 2012 15:40
To: cghersi
Subje
> Is there any effective way to directly retrieve the ID of the just added
> object after the context.commitChanges() invocation?
After commit the ID should be available via normal Cayenne APIs (e.g.
Cayenne.inPkForObject). So there's something else at play too.
Andrus
On Mar 9, 2012, at 9:10 A
If it were me, I would add a status column to the Test table
(approved, pending-approval, maybe rejected).
Then I would store both approved tests and pending-approval tests in
the same tables rather than using identical temporary tables.
You might also consider adding a related_parent_test_id colu
Hi all, perhaps Ive understood something about the issue:
Seems that the problem arises when I add a new object to the DB: just after
the insert, I need the autogenerated PK, and this seems to put in troubles
the method DataObjectUtils.intPKForObject(Persistent);
Which sometimes throws the Excep
