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 administration is done in WO, the > customer's home page was coded in PHP by someone else (other company), > accessing the same DB (read only). Using MySQL was a customer requirement > when the project started. > > The PHP stuff depends on MySQL's FULLTEXT search (with a custom stopwords > configuration), which in turns requires the use of MYISAM. I'd really like to > move the whole DB to InnoDB tables, but I have no clue how to keep the > FULLTEXT stuff of the PHP part functional. > > It would be no problem to change the WO or PHP code (for which I now also > have the honor to maintain) as long the stuff continues to work as expected. > > Any ideas?
Timo, I know it's ugly, but you can mix InnoDB and MyISAM tables in the same database. If the FULL TEXT indexes are only on a single/few tables/columns that may be an option. Keep MyISAM for the FT tables, move everything else to InnoDB. ;david -- David LeBer Codeferous Software 'co-def-er-ous' adj. Literally 'code-bearing' site: http://codeferous.com blog: http://davidleber.net profile: http://www.linkedin.com/in/davidleber twitter: http://twitter.com/rebeld -- Toronto Area Cocoa / WebObjects developers group: http://tacow.org _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
