Never leave foreign keys, indexes, or anything else that the database should do
to PHP.
http://www.classoutfit.com/articles/2010/02/cakephp-basic-database-table-tuning-tips/
Jeremy Burns
jeremybu...@me.com
(Skype) +44 208 123 3822 (jeremy_burns)
(m) +44 7973 481949
(h) +44 208 530 7573
On 13 Ma
Yeah, but beside that, does CakePHP use some of the features that come
with InnoDB (like foreign keys using the database engine instead of
implementing it in PHP)? Basically I'm curios is if there is some
gain, beside transactions and row locking instead of table locking,
that would seriously impac
Row locking instead of table locking.
On Mar 12, 8:25 am, "Dr. Loboto" wrote:
> Transactions, as always.
>
> On Mar 12, 6:04 pm, Varga Levente wrote:
>
> > Hello!
>
> > Is something gained if instead of MyISAM engine the InnoDB is used with
> > CakePHP?
>
> > levi
>
> > --
> > Lege, lege, releg
Transactions, as always.
On Mar 12, 6:04 pm, Varga Levente wrote:
> Hello!
>
> Is something gained if instead of MyISAM engine the InnoDB is used with
> CakePHP?
>
> levi
>
> --
> Lege, lege, relege, ora, labora et invenies.
Check out the new CakePHP Questions site http://cakeqs.org and help ot
Hello!
Is something gained if instead of MyISAM engine the InnoDB is used with CakePHP?
levi
--
Lege, lege, relege, ora, labora et invenies.
Check out the new CakePHP Questions site http://cakeqs.org and help others with
their CakePHP related questions.
You received this message because you
