10 messages in com.mysql.lists.bugsRe: Repeatable mysql 'update' bug - l...
FromSent OnAttachments
Sander Pilon18 May 2000 08:14 
Sander Pilon18 May 2000 10:00 
Dana Powers18 May 2000 10:33 
Sander Pilon18 May 2000 10:54 
Thimble Smith18 May 2000 14:35 
sas...@mysql.com18 May 2000 15:53 
sas...@mysql.com18 May 2000 15:57 
Sander Pilon18 May 2000 16:10 
sas...@mysql.com18 May 2000 16:21 
Michael Widenius22 May 2000 04:48 
Subject:Re: Repeatable mysql 'update' bug - lockup / cpu drain.
From:sas...@mysql.com (sas@mysql.com)
Date:05/18/2000 03:57:28 PM
List:com.mysql.lists.bugs

Dana Powers wrote:

I can verify that this causes an error in 3.22.29, but it works just fine with 3.23.16.

So does this warrant a new release of 3.22, or is the solution to upgrade to 3.23 even though it isnt a fully stable system?

I would recommend an upgrade to 3.23. There are certain bugs that we will not fix in 3.22 if they are found, but all bugs will be fixed in 3.23 until it reaches the officially stable status.

I havent had any problems with 3.23.16, and as has been said on this list before, it is equally or more stable than 3.22 for anything that 3.22 did, but maybe not production level on all new features (such as BDB transactions, binary replication etc).

Correct.

SELECT 3-22.feature,3-22.stability,3-23.stability FROM 3-22 LEFT JOIN 3-23 ON 3-22.feature = 3-23.feature;

On the above query you will actually get higher than 3-22 stability.

-- Sasha Pachev

+------------------------------------------------------------------+ | /*/\*\/\*\ /*/ \*\ /*/ \*\ |*| Sasha Pachev | | /*/ /*/ /*/ \*\_ |*| |*||*| mailto:sas@mysql.com | | /*/ /*/ /*/\*\/*/ \*\|*| |*||*| Provo, Utah, USA | | /*/ /*/ /*/\*\_/*/ \*\_/*/ |*|____ | | ^^^^^^^^^^^^/*/^^^^^^^^^^^\*\^^^^^^^^^^^ | | /*/ \*\ Developers Team | +------------------------------------------------------------------+