On Mon 2003-01-27 at 19:02:20 -0800, [EMAIL PROTECTED] wrote:
[...]
> > That would be rather be at least 6 weeks, because since 2002-12-14
> > (v4.0.6) MySQL is declared gamma.
> 
> That's about right, actually. I was going to check back, to see if the
> development status had changed in the interim, but didn't. Shame on me. I
> updated my version to the Gamma 4.0.6 earlier this evening and will be
> testing it on my development box tonight. 

You are aware that 4.0.9 is current?

> > I am not sure why you *had* to rebuild indexes. AFAIK, MySQL 4.0.x
> > should work on tables created with 3.23.x (aveats below ;)
> 
> I'm relatively certain that was an anomaly that came from the
> tarball I used to copy the files over, rather than something wrong
> with the indexes themselves or the method which 4.0.x reads and
> writes to them. I tried replicating the original error just now with
> the Gamma release and the problem didn't reoccur.

So it's also possible that it was a glitch in the beta version you
used before and that was fixed in the meantime. The out-of-the-box
comment is only meant for the most recent version, 4.0.9, of course.

[...]
> Tongue-in-cheek rules to remember when testing the Gamma:
> 
> 1. Wear a hair net to hold your hair in place. There are recorded instances of
> people being plucked bald by the sheer speed of the newest releases using the
> cache. 

*lol*

HAND,

        Benjamin.


Attachment: msg65048/pgp00000.pgp
Description: PGP signature

Reply via email to