Thanks francky06l,
But atomic is set to true by default (according to the
documentation), and I have already traced the DB calls, as you can
read above. The ROLLBACK is being called, but it's not affecting the
INSERT operation, because a SELECT is being made after.
Is that a bug?
I do not know if it's a bug, I do have transactional calls as well but
I use innoDb type table. It seems that the select is triggering an
auto-commit on ISAM. I am not sure actually, but try setting your
table as innoDb and check if you get the same result.
Maybe you could also try to validate
There is no auto-commit in MyISAM tables, because MyISAM doesn't
support transactions at all! All transaction statements are ignored by
this storage engine. That is why rollback does nothing. InnoDB has
more advantages to MyISAM than transaction support. It also does row
locking (MyISAM has only
Hi group,
I'm not sure if I'm misunderstoonding something or if I've found a bug
in /libs/model/model.php.
It happens when I use saveAll() to save a bunch of records of the same
model:
$this-Mymodel-saveAll($this-data['Mymodel'], array('validate' =
'first'))
This should do two things:
1.-
BTW I'm using Cake 1.2.0.7125 RC1 (model.php revision 7118)
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
CakePHP group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this
If you set atomic = true, it should work since it will issue a
rollback for transaction.
Can you set debug to 2 and look at the DB traces
I guess your table are in ISAM, try with innoDb
hth
On Jun 14, 2:25 pm, Jaime [EMAIL PROTECTED] wrote:
BTW I'm using Cake 1.2.0.7125 RC1 (model.php revision
