Re: MySQL: Moving to InnoDB

2010-01-14 Thread Kieran Kelleher
Clever. Thanks for sharing. Regards, Kieran :-) On Jan 14, 2010, at 9:45 AM, Timo Hoepfner wrote: > Ok, went a bit different way. I added a myisam table and added triggers for > insert/update/delete on the (now) innodb table to put a copy in the myisam > table which now has the fulltext index.

Re: MySQL: Moving to InnoDB

2010-01-14 Thread Timo Hoepfner
Ok, went a bit different way. I added a myisam table and added triggers for insert/update/delete on the (now) innodb table to put a copy in the myisam table which now has the fulltext index. As the app is read-mostly, the additional load is not a problem. The PHP query needed to be adjusted

Re: MySQL: Moving to InnoDB

2010-01-13 Thread Kieran Kelleher
Hi Timo, If you mix MyISAM and InnoDB, then when a transaction fails, IIRC, just he InnoDB tables will rollback, the MyISAM tables will not. If important,to you, then you could potentially write some logic that if an ec save fails, then do some logic to delete the rows (EOs) inserted into the M

Re: MySQL: Moving to InnoDB

2010-01-13 Thread Chuck Hill
On Jan 13, 2010, at 4:28 PM, Travis Britt wrote: On Jan 13, 2010, at 6:51 PM, Chuck Hill wrote: Row size limit? Oooh, tell me more! ;-) When I physicalize Oracle or MySQL I often imagine this hulking, idiosyncratic Soviet-era metal contraption that in the hands of its builders will re

Re: MySQL: Moving to InnoDB

2010-01-13 Thread Travis Britt
On Jan 13, 2010, at 6:51 PM, Chuck Hill wrote: > Row size limit? Oooh, tell me more! ;-) When I physicalize Oracle or MySQL I often imagine this hulking, idiosyncratic Soviet-era metal contraption that in the hands of its builders will relocate mountains but which I am forced to drive to pick

Re: MySQL: Moving to InnoDB

2010-01-13 Thread Chuck Hill
On Jan 13, 2010, at 3:11 PM, Travis Britt wrote: Yeah I'm doing this, everything is InnoDB except for a read-mostly (as in, write once in a blue moon) table that's MyISAM due to InnoDB's row size limit Row size limit? Oooh, tell me more! ;-) and the fact that it's currently got a ton

Re: MySQL: Moving to InnoDB

2010-01-13 Thread Travis Britt
Yeah I'm doing this, everything is InnoDB except for a read-mostly (as in, write once in a blue moon) table that's MyISAM due to InnoDB's row size limit and the fact that it's currently got a ton of varchar(255) columns. On Jan 13, 2010, at 4:01 PM, David LeBer wrote: > I know it's ugly, but you

Re: MySQL: Moving to InnoDB

2010-01-13 Thread David LeBer
On 2010-01-13, at 3:52 PM, Timo Hoepfner wrote: > Hi list, especially Kieran. :) > > I have a project that evolved over the years. Basically it's a product and > image database, which also provides the content for the customer's home page. > The product and image database and CMS administratio

MySQL: Moving to InnoDB

2010-01-13 Thread Timo Hoepfner
Hi list, especially Kieran. :) I have a project that evolved over the years. Basically it's a product and image database, which also provides the content for the customer's home page. The product and image database and CMS administration is done in WO, the customer's home page was coded in PHP