Zend Framework

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.5.0
• Fix Version/s: 1.8.0
• Component/s: Zend_Db_Table
• Labels:

  None

http://framework.zend.com/manual/en/zend.db.table.relationships.html#zend.db.table.relationships.cascading

"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.

• Assignee:

  Ralph Schindler

  Reporter:

  Lewis Johnston

• Created:

  21/Mar/08 11:53 AM

  Updated:

  07/Jan/09 4:56 PM

  Resolved:

  07/Jan/09 4:56 PM