organizational use only) web application we built recently I used
InnoDB so I could guarantee referential integrity and also so I could
use transactions. The added benefit was that another application could
also use the same database and I wouldn't have to worry as much about
data getting corrupted. For most public facing web applications I use
MyISAM for speed and scalability and try to design the application so
it doesn't need to have the database guarantee referential integrity
or need transactions. Zend_Db_Table will take care of relationships,
but (as far as I understand) it can't take care of them
transactionally (since it's working in PHP, not at the database
level). If you need a guarantee that referential integrity will be
maintained, you should use InnoDB. If you use MyISAM, your application
needs to account for the possibility of referential integrity being
broken, even if defining your relationships using Zend_Db_Table.
Someone else can probably explain the reasons behind this a little
better :-)
On Sat, Jun 13, 2009 at 6:11 AM, iceangel89<comet2005@gmail.com> wrote:
>
> i heard MyISAM is faster but less reliable as data grows. InnoDB is slower
> but more reliable with ACID and support for relationships. so which do u
> use? InnoDB seems like a better choice for reliability, so long term ... but
> its slower? and if i use Zend_Db_Table, it will take care of relationships
> right?
>
> so the qn is what do u use?
> --
> View this message in context: http://www.nabble.com/What-MySQL-Storage-Engine-to-use-tp24011061p24011061.html
> Sent from the Zend DB mailing list archive at Nabble.com.
>
>
--
Bradley Holt
bradley.holt@foundline.com
没有评论:
发表评论