Foreign key has nothing to do with innoDB, but transaction has ... 3 solutions:
- save current data before saving and roll back yourself (costive) - accept the integrity potential defect, have a "batch job" to control and correct - have a transactional DB On Apr 11, 6:56 pm, "Mariano C." <[email protected]> wrote: > My DB server doesn't support innodb engine, so I can't use Foreign key > costraint. > How can I assure referential intergrity? Can I do this using cakephp, > how? -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/cake-php
