Pete Harlan wrote:
> My two cents: Just upgrade. We hammer on it pretty hard and the
> transition has not only been smooth, it's been a delight. The query
> cache, on our load, handles 60% of the queries, which I never imagined
> would happen.
>
> 4.0.18 feels as boringly stable as most released
unstable.
>
> But I like the new query-cache. So, I wonder, how stable is 4.0.18 really?
> (compared to 3.23.58). Since I read that I need to upgrade DBD:mysql for all
> Perl clients as well, I am not too keen to just give it a whirl, only to
> find
> out I upgraded to a poten
stable is 4.0.18 really?
(compared to 3.23.58). Since I read that I need to upgrade DBD:mysql for all
Perl clients as well, I am not too keen to just give it a whirl, only to
find
out I upgraded to a potential lemon.
Counting on an honest assessment (and not the promo rap), how stable is it,
really
Hello,
I am long since using MySQL 3.23.58; and it works perfectly. In fact, it
works so well, that I have always been very hesitant to upgrade to the 4.x
series. Especially, since 4.x, a year ago or so, was still rather unstable.
But I like the new query-cache. So, I wonder, how stable is
