Use InnoDB. As John says, it won't let you create RI between fields with different types (and it's very precise) and you get transactions thrwn in for good measure.
On 2 Nov 2011, at 16:14, Jon Bennett wrote: >> I've had some similar trouble with 2.0 >> turned out the fields in the DB were not the same type. >> id on one table was a bigint and the foreign key on the relationship table >> was a regular integer. >> atenciosamente, > > With MySQL you can catch these errors at db schema level if you use > foreign key constraints, as you can't connect columns of different > types. > > -- > 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 > cake-php+unsubscr...@googlegroups.com For more options, visit this group at > http://groups.google.com/group/cake-php -- 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 cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php
