Task #217 — Transactions don't seem to delete created objects
Attached to Project— EZPDO
Opened by João Samuel Nunes Lopes (jsnl85) - Monday, 5 Feb 2007, 12:05pm
Last edited by oak nauhygon (admin) - Monday, 5 Feb 2007, 1:51pm
Last edited by oak nauhygon (admin) - Monday, 5 Feb 2007, 1:51pm
| Bug Report | |
| Runtime API | |
| Assigned | |
| xman101 (xman101) | |
| Windows |
| High | |
| Normal | |
| CVS | |
| 1.1.x | |
|
I try to create an object that is composed_of other objects. What i do is something like this: reproduction of the bug: >>> class Object1 { /** * @orm val char(16) unique(idx_val) */ public $val; /** * @orm obj2 composed_of one Object2 */ public $obj2; } class Object2 { /** * @orm val char(64) */ public $val; } $pm = epManager::instance(); $dsn = DB_TYPE.'://'.DB_USERNAME.((DB_PASSWORD != '') ? ':'.DB_PASSWORD : '').'@'.DB_HOST.'/'.DB_NAME; $pm->setDsn($dsn); try { $db->start_t(); $obj2 = $pm->create('Object2'); $obj2->val = 'hello world'; $obj1 = $pm->create('Object1'); $obj1->val = 'obj1'; $obj1->obj2 = $obj2; $db->commit_t(); } catch(Exception $ex) { echo '<p>exception...</p>'; } exit(-1); <<< The object2 class has a var that is unique. I have a problem when object2 is duplicate in datastore (execute the script more than once): object2 is not created like it is supposed to happen, but object1 is created and not deleted from datastore after a rollback... By the way.. i tried to explicitly delete object2 but didn't work.. |
This task depends upon
This task blocks these from closing
Comments (1) | Attachments (0) | Related Tasks (0/0) | Notifications (3) | Reminders (0) | History |
Comment by João Samuel Nunes Lopes - Monday, 5 Feb 2007, 12:08pm
correction:
The object1 class has a var that is unique.
I have a problem when object1 is duplicate in datastore (execute the script more than once): object1 is not created like it is supposed to happen, but object2 is created and not deleted from datastore after a rollback...