Ok i will try to do it in a smarter way, but clear that is hard on
Monday morning ;)
Andrus Adamchik wrote:
From the example in your message, you do not the *exiting*
MasterScheduleAux objects, you still delete the old ones, and
reinsert them back.
This of course should read "modify the ex
From the example in your message, you do not the *exiting*
MasterScheduleAux objects, you still delete the old ones, and
reinsert them back.
This of course should read "modify the existing MasterScheduleAux
objects". Monday morning, tough time :-)
Andrus
On Jul 21, 2008, at 10:26 AM,
On Jul 18, 2008, at 7:03 PM, Laurent Marchal wrote:
I managed to modify directly the object, removing the relation from
MasterSchedule->MasterScheduleAux after deleting
the MasterScheduleAux object.
From the example in your message, you do not the *exiting*
MasterScheduleAux objects, you
I managed to modify directly the object, removing the relation from
MasterSchedule->MasterScheduleAux after deleting
the MasterScheduleAux object.
But the transaction do the DELETE after the INSERTs, so some fresh
inserted items are deleted.
And i still have "snapshot version changed, don't kn
Ok i will try to modify the object directly, and see the results.
I will post code if this doesn't work.
Andrus Adamchik wrote:
On Jul 18, 2008, at 5:10 PM, Laurent Marchal wrote:
Hi !
I would like to do some DELETEs and INSERTs in one transaction, but
since DELETE is made after the INSERTs
On Jul 18, 2008, at 5:10 PM, Laurent Marchal wrote:
Hi !
I would like to do some DELETEs and INSERTs in one transaction, but
since DELETE is made after the INSERTs, it deletes the fresh
inserted values...
Yeah, weird. Could you post some sample code? Looking at your log, you
delete a d
Hi !
I would like to do some DELETEs and INSERTs in one transaction, but
since DELETE is made after the INSERTs, it deletes the fresh inserted
values...
Is there a way to force cayenne to do DELETE before all others
operations when a commit occurs ?
What means the "snapshot version chan
