MyISAM supports FullText indexes, and (supposedly) faster / more accurate COUNT(*) results. If either of those are important to you, you might want to stick with MyISAM.
--
-Hector
I personally prefer InnoDB primarily because of the constraints, but it's up to you and what fits your data.
Let's say I switch my db to InnoDB. What 'll it return when I try to delete a parent row when it exists in a child row? Just 'false'?
No, MySQL will report an error, which you can test for in your PHP code:
<?php
try {
$row->delete();
} catch (Exception $e) {
// Unable to delete row, possibly due to foreign key constraint
}
?>
On Fri, Oct 17, 2008 at 9:31 AM, EducatedFool <wimkumpen@hotmail.com> wrote:
Hector Virgen wrote:
>
> restricting the deletion of parent rows when child rows exist.
Let's say I switch my db to InnoDB. What 'll it return when I try to delete
a parent row when it exists in a child row? Just 'false'?
Can someone say why I just have to keep with MyISAM? Why is that better?
About cascade delete: In my opinion the framework needs to folow the
reference map through all the levels. Don't see why it wouldn't...:-)
View this message in context: http://www.nabble.com/Referencemap%3A-delete-CASCADE-tp20027817p20036747.html
Sent from the Zend DB mailing list archive at Nabble.com.
--
-Hector
没有评论:
发表评论