Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 2.5.0b5

Bug #17065 There is no NEW row in on DELETE trigger
Submitted: 2010-02-04 10:19 UTC
From: irangame Assigned: quipo
Status: Closed Package: MDB2
PHP Version: 5.3.0 OS: Windows XP SP2
Roadmaps: (Not assigned)    
Subscription  


Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know! Just going to say 'Me too!'? Don't clutter the database with that please !
Your email address:
MUST BE VALID
Solve the problem : 7 + 30 = ?

 
 [2010-02-04 10:19 UTC] irangame (Mojtaba Ebrahimi)
Description: ------------ I wanna to run a Schema XML file. DB Driver->MySQL 5.1.33 Test script: --------------- $result = $schema->installSchema($main_file, $variables, $base_file, $data, $create, $debug); Expected result: ---------------- MDB2 Error: not found : _doQuery: [Error message: Could not execute statement] [Last executed query: CREATE TRIGGER test_pk_delete_trg BEFORE DELETE ON test1 FOR EACH ROW BEGIN SET FOREIGN_KEY_CHECKS = 0; IF (SELECT `test2`.test_id AS test_id FROM `test2` WHERE test_id = OLD.id) IS NOT NULL AND (NEW.id <> OLD.id) THEN CALL delete_ON_TABLE_test2_VIOLATES_FOREIGN_KEY_CONSTRAINT(); END IF; SET FOREIGN_KEY_CHECKS = 1; END;] [Native code: 1363] [Native message: There is no NEW row in on DELETE trigger]

Comments

 [2010-02-04 10:25 UTC] irangame (Mojtaba Ebrahimi)
 [2010-08-17 21:12 UTC] ifeghali (Igor Feghali)
-Package: MDB2_Schema +Package: MDB2
Looks to me an error on MDB2 end. It is not handling properly the creation of ON DELETE triggers. This can be relevant: http://forums.mysql.com/read.php?99,252405,252405
 [2010-08-29 14:31 UTC] quipo (Lorenzo Alberton)
-Status: Open +Status: Closed -Assigned To: +Assigned To: quipo
This bug has been fixed in SVN. If this was a documentation problem, the fix will appear on pear.php.net by the end of next Sunday (CET). If this was a problem with the pear.php.net website, the change should be live shortly. Otherwise, the fix will appear in the package's next release. Thank you for the report and for helping us make PEAR better.