I'm using symfony 1.2 / Propel 1.3 / MySQL (MyISAM) and have a table
defined with the following <foreign-key> entry:
<foreign-key name="fk_user_event_application_event_approval_status"
foreignTable="event_approval_status" onDelete="restrict">
<reference local="approval_status_id" foreign="id"/>
</foreign-key>
The onDelete="restrict" attribute doesn't seem to generate any code to
enforce the desired constraint. If I change the attribute to
onDelete="setnull" - that works. But its obviously not what I want.
According to the Propel 1.3 docs (http://propel.phpdb.org/trac/wiki/
Users/Documentation/1.3/Relationships - On Update and On Delete
Triggers ). "For databases that do not support foreign keys, this
functionality will be emulated by Propel."
Anybody else run into this? Am I missing something?
In my propel.ini I have:
propel.mysql.tableType = MyISAM
propel.addVendorInfo = true
propel.addGenericAccessors = true
propel.addGenericMutators = true
propel.addTimeStamp = true
propel.addValidators = false
propel.addHooks = true
propel.useDateTimeClass = true
propel.defaultTimeStampFormat = Y-m-d H:i:s
propel.defaultTimeFormat = H:i:s
propel.defaultDateFormat = Y-m-d
propel.schema.validate = false
propel.samePhpName = false
propel.disableIdentifierQuoting = false
propel.emulateForeignKeyConstraints = true
--
You received this message because you are subscribed to the Google Groups
"symfony users" group.
To post to this group, send email to symfony-us...@googlegroups.com.
To unsubscribe from this group, send email to
symfony-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/symfony-users?hl=en.
