Selecting MySQL engine (InnoDB/MyISAM) when creating models

2007-02-13 Thread yary
There's a thread from June 28 '06 on this list about changing MySQL's storage engine from InnoDB to MyISAM for a particular table/model. Now, an InnoDB table respects foreign keys, and a MyISAM table ignores them. An "ALTER TABLE ... ENGINE = MyISAM" statement will fail if the table has any forei

Re: Selecting MySQL engine (InnoDB/MyISAM) when creating models

2006-06-29 Thread Geert Vanderkelen
James Bennett wrote: > On 6/28/06, Geert Vanderkelen <[EMAIL PROTECTED]> wrote: >> I'm also not sure how you going to use the full text >> searching unless there is a patch now too.. > > For just querying against the DB, having fulltext indexes set up > should be sufficient; the DB's query optimi

Re: Selecting MySQL engine (InnoDB/MyISAM) when creating models

2006-06-28 Thread Adrian Holovaty
On 6/28/06, Geert Vanderkelen <[EMAIL PROTECTED]> wrote: > ALTER TABLE appname_modelname ENGINE=MyISAM; > > and you're done. That's something you'll have to do afterward doing a > 'syncdb' or sqlreset indeed. You can put that ALTER TABLE statement in the "sql" directory within your app, named in

Re: Selecting MySQL engine (InnoDB/MyISAM) when creating models

2006-06-28 Thread James Bennett
On 6/28/06, Geert Vanderkelen <[EMAIL PROTECTED]> wrote: > I'm also not sure how you going to use the full text > searching unless there is a patch now too.. For just querying against the DB, having fulltext indexes set up should be sufficient; the DB's query optimizer will recognize that there's

Re: Selecting MySQL engine (InnoDB/MyISAM) when creating models

2006-06-28 Thread James Bennett
On 6/28/06, Geert Vanderkelen <[EMAIL PROTECTED]> wrote: > Think you made a typo there or so.. > > MyISAM -> none transactional > InnoDB and NDBCluster (and BDB) -> transactional Yeah. Too much traveling, too much coding, too little sleep :( -- "May the forces of evil become confused on the way

Re: Selecting MySQL engine (InnoDB/MyISAM) when creating models

2006-06-28 Thread Geert Vanderkelen
Hi Andrew, [EMAIL PROTECTED] wrote: > Hi, > > A total newbie question here, but is there a way to specify the engine > I would prefer when defining models for applications. Would really > prefer MyISAM, but MySQL keeps creating InnoDB when the tables are > automatically created. (Reason: MyISAM

Re: Selecting MySQL engine (InnoDB/MyISAM) when creating models

2006-06-28 Thread Geert Vanderkelen
Hi James, James Bennett wrote: > On 6/28/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: >> A total newbie question here, but is there a way to specify the engine >> I would prefer when defining models for applications. Would really >> prefer MyISAM, but MySQL keeps creating InnoDB when the tabl

Re: Selecting MySQL engine (InnoDB/MyISAM) when creating models

2006-06-28 Thread James Bennett
On 6/28/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > A total newbie question here, but is there a way to specify the engine > I would prefer when defining models for applications. Would really > prefer MyISAM, but MySQL keeps creating InnoDB when the tables are > automatically created. (Reas

Selecting MySQL engine (InnoDB/MyISAM) when creating models

2006-06-28 Thread [EMAIL PROTECTED]
Hi, A total newbie question here, but is there a way to specify the engine I would prefer when defining models for applications. Would really prefer MyISAM, but MySQL keeps creating InnoDB when the tables are automatically created. (Reason: MyISAM supports full-text searching whereas InnoDB doesn