Using SELECT ... FOR UPDATE and
ROLLBACK could cause
mysqld to hang indefinitely.
(Bug#28165)
Concurrent updates on two different connections could lead to an
assertion failure.
(Bug#28090)
Updating a row within a table that has a unique compound index
to a non-unique value would not raise an error.
(Bug#27997)
Rolling back an inserted row while accessing the same on a
different connection would cause a crash.
(Bug#27993)
Creating a table with a 19 digit DECIMAL
column would cause incorrect data to be stored. This is due to
current limitation in Falcon where you cannot create a table
with a column with greater than 18 digits precision (i.e.
DECIMAL(18,9)). Creating a column with larger
than this specification will fail and raise an error.
(Bug#27962)
Executing INSERT INTO ... SELECT FROM could
cause a crash on large data sets.
(Bug#27951)
Inserting data into the same table on two different connections
with autocommit disabled would cause a crash.
(Bug#27895)
Creating a Falcon table immediately after creating a new
database could cause a crash.
(Bug#27768)
Executing SELECT ... FOR UPDATE in a second
connection on a newly created and populated table could cause a
crash.
(Bug#27767)
Continually updating a BLOB column would
cause MySQL server to crash.
(Bug#27719)
Using a trigger on an UPDATE to a Falcon
table when autocommit is disabled would cause MySQL server to
crash.
(Bug#27574)
Interrupting a stored procedure during execution could cause a
crash.
(Bug#27539)
Opening the same database with Falcon tables on a different
connection could cause a crash.
(Bug#27428)
Using ROLLBACK after a
DELETE does not restore the deleted row.
(Bug#27357)
Two simultaneous SELECT ... FOR UPDATE
statements with READ-COMMITTED isolation
level would result in the wrong error message being returned.
(Bug#26871)
Row insertions to a table with long VARCHAR
columns and large compound indexes would cause MySQL to crash.
(Bug#26850)
User Comments
Add your own comment.