ZF-2940: self::NO_ACTION documented but not implimented

Issue Type: Bug Created: 2008-03-21T11:53:44.000+0000 Last Updated: 2009-01-07T16:56:27.000+0000 Status: Resolved Fix version(s): - 1.8.0 (30/Apr/09)

Reporter: Lewis Johnston (orangehairedboy) Assignee: Ralph Schindler (ralph) Tags: - Zend_Db_Table

Related issues: Attachments:


"No cascading update is done in the example below if the primary key value in the parent class is changed. The 'onUpdate' element of the reference map entry is self::RESTRICT. You can get the same result using the value self::NO_ACTION, or by omitting the 'onUpdate' entry."

The self::NO_ACTION constant is not defined in Zend_Db_Table_Abstract, but it is documented.

Either a) implement this or b) remove it from the documentation and inform users clearly that if onUpdate and onDelete are not specified, no cascading will be performed. The documentation causes some confusion here - it could be read that by declaring $_dependentTables that cascading WILL happen UNLESS you you specify self::NO_ACTION, but glancing at the source - this does not seem to be the case.


Posted by Wil Sinclair (wil) on 2008-03-25T20:43:51.000+0000

Please categorize/fix as needed.

Posted by Wil Sinclair (wil) on 2008-12-04T13:17:29.000+0000

Reassigning to Ralph since he's the new maintainer of Zend_Db

Posted by Benjamin Eberlei (beberlei) on 2009-01-07T16:56:26.000+0000

fixed by dropping the reference to self::NO_ACTION

Have you found an issue?

See the Overview section for more details.


© 2006-2018 by Zend, a Rogue Wave Company. Made with by awesome contributors.

This website is built using zend-expressive and it runs on PHP 7.