>
To: <[EMAIL PROTECTED]>
Sent: Saturday, August 04, 2001 9:54 AM
Subject: Re: Thinking of switching from MyISAM to InnoDB
> On Saturday 04 August 2001 09:25, Sinisa Milivojevic wrote:
>
> > Nick Seidenman writes:
> > > Apparentlly there's a 4 GB limit to a MyIS
Is there a place that outlines the advantages/disadvantages of both
MyISAM and InnoDB?
Thanks,
Chris
-Original Message-
From: Tonu Samuel [mailto:[EMAIL PROTECTED]]
Sent: Saturday, August 04, 2001 2:34 PM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: Thinking of switching from
On 04 Aug 2001 16:25:14 +0300, Sinisa Milivojevic wrote:
> There is no 4 Gb limit in MyISAM with later 3.23 versions.
>
> This limit is imposed by a filesystem only.
and RAIDed table can help to build aby size tables if only index
file doesn't get too big.
Actually InnoDB is nice thing.
On Sat, Aug 04, 2001 at 09:15:52AM -0500, Gerald R. Jensen wrote:
>
> To the best of my knowledge, MySQL doesn't impose file size limits
> ... that is dictated by the O/S's file system. Switching to InnoDB
> wouldn't change that.
But InnoDB would let you use multiple tablespaces to get around an
On Saturday 04 August 2001 09:25, Sinisa Milivojevic wrote:
> Nick Seidenman writes:
> > Apparentlly there's a 4 GB limit to a MyISAM file when the table it
> > contains has VARCHAR, TEXT, or BLOB columns. In order to get around this
>
> There is no 4 Gb limit in MyISAM with later 3.23 versions.
t; <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, August 03, 2001 6:44 PM
Subject: Thinking of switching from MyISAM to InnoDB
Apparentlly there's a 4 GB limit to a MyISAM file when the table it contains
has VARCHAR, TEXT, or BLOB columns. In order to get around this limit
Nick Seidenman writes:
>
> Apparentlly there's a 4 GB limit to a MyISAM file when the table it contains
> has VARCHAR, TEXT, or BLOB columns. In order to get around this limitation I
> was looking to switching to InnoDB table types. As this looks like a
> relatively new subsystem I'm wonderi
Apparentlly there's a 4 GB limit to a MyISAM file when the table it contains
has VARCHAR, TEXT, or BLOB columns. In order to get around this limitation I
was looking to switching to InnoDB table types. As this looks like a
relatively new subsystem I'm wondering if it is stable enough for pro
