5329c3827c
* Fixed a few layout bugs in new documentation * Fixed documentation table of contents indentation bug in IE6 (fixes #344) * Fixed a parser bug in Sensei_Doc_Section * Restructrured a bit some files of the documentation.
15 lines
761 B
PHP
15 lines
761 B
PHP
Doctrine supports aggregates and composites. When binding composites you can use methods Doctrine_Record::ownsOne() and Doctrine_Record::ownsMany(). When binding
|
|
aggregates you can use methods Doctrine_Record::hasOne() and Doctrine_Record::hasMany(). Basically using the owns* methods is like adding a database level ON CASCADE DELETE
|
|
constraint on related component with an exception that doctrine handles the deletion in application level.
|
|
|
|
|
|
|
|
In Doctrine if you bind an Email to a User using ownsOne or ownsMany methods, everytime User record calls delete the associated
|
|
Email record is also deleted.
|
|
|
|
|
|
|
|
Then again if you bind an Email to a User using hasOne or hasMany methods, everytime User record calls delete the associated
|
|
Email record is NOT deleted.
|
|
|