MySQL 4.1.x Rleease

[Arc]

Sorry if this has been gone over before, but I checked google groups and I
couldn't find anything.

Does anyone here have any idea when 4.1.x will be released into production
(i.e. come out of beta). It is currently impossible to find a commercial web
host who supports it because it is in beta, even though it has been out for
a long time now.

My system *requires* subqueries, and so I can't even host it until 4.1.x is
released to production.

On the other hand, anyone know of a reputable web host that provides MySQL
4.1.x as an option?

TIA,
Arc

[Bill Karwin]

Arc wrote:

Sorry if this has been gone over before, but I checked google groups and I
couldn't find anything.

Does anyone here have any idea when 4.1.x will be released into production
I don't think even MySQL AB can offer a date that is carved in stone.
Think of any software company you have ever been involved with. It
would not do for any company to quote a date, until they are positive
that the product is done and ready to ship. Otherwise, they'd have to
risk either changing the date and upsetting people who were depending on
the release, or else shipping a product that wasn't ready. Not good,
either way.

I've always had the attitude, don't rely on technology that isn't
available yet.
It is currently impossible to find a commercial web
host who supports it because it is in beta, even though it has been out for
a long time now.
Keep in mind that it might take some significant amount of time before
*any* ISP upgrades their hosting support to MySQL 4.1.x. There are some
significant issues between 4.0 and 4.1 (such as the PASSWORD()
encryption function) that make the upgrade nontrivial without breaking
some existing applications.
My system *requires* subqueries, and so I can't even host it until 4.1.x is
released to production.

Many queries that use subqueries can be rewritten:

- as joins of some sort (see
http://dev.mysql.com/doc/mysql/en/Re...queries.html);

- as two separate queries: get the result of the subquery in the first,
make a string of comma-separated values out of it, and then use that in
the second query (for instance, in an IN( ) predicate);

- as an initial query, then a loop on the result set, executing the
second query for each value -- this can simulate correlated subqueries.

Of course, these are less convenient than using the subquery syntax, but
they do work in previous versions of MySQL.

Regards,
Bill K.

[Arc]

Thanks for the info Bill!

Regards, Arc