• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: MySQL: Moving to InnoDB
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: MySQL: Moving to InnoDB


  • Subject: Re: MySQL: Moving to InnoDB
  • From: Travis Britt <email@hidden>
  • Date: Wed, 13 Jan 2010 18:11:06 -0500

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 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.

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Follow-Ups:
    • Re: MySQL: Moving to InnoDB
      • From: Chuck Hill <email@hidden>
References: 
 >MySQL: Moving to InnoDB (From: Timo Hoepfner <email@hidden>)
 >Re: MySQL: Moving to InnoDB (From: David LeBer <email@hidden>)

  • Prev by Date: Modeling an optional to-one relationship
  • Next by Date: Re: Modeling an optional to-one relationship
  • Previous by thread: Re: MySQL: Moving to InnoDB
  • Next by thread: Re: MySQL: Moving to InnoDB
  • Index(es):
    • Date
    • Thread