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 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).
SELECT 3-22.feature,3-22.stability,3-23.stability
FROM 3-22
LEFT JOIN 3-23
ON 3-22.feature = 3-23.feature;
IMO, a 3.22 patch should be released. Why? 3.22 is marketed as 'stable'
release and
contains reproducable lockups. These things do not belong in 'stable'
releases :)
So... you are saying that 3.32.16 is as stable as 3.22.32, as long as I dont
use any of the new
tricks?
Sander
10 messages in com.mysql.lists.bugsRE: Repeatable mysql 'update' bug - l...