SELECT ... FOR UPDATE is now supported.

Uncommitted record scavenging has been implemented.

Performance diagnostics are available through INFORMATION_SCHEMA.

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)

Falcon could consume large amounts of memory during a high number of continuous INSERT statements. (Bug#26843)

Updating a partitioned table in two sessions simultaneously would cause MySQL to crash. (Bug#26828)

Locking between sessions when using SELECT ... FOR UPDATE would not work. (Bug#26826)

Tables with UNIQUE key constraints would not be enforced. (Bug#26803)

When updating a table with a unique key constraint the constraint would not be enforced. (Bug#26802)

Searching for records in a table with a DECIMAL(6,6) column would fail to find the value. (Bug#26469)

Rows with a numeric column may fail to find records with zero values. (Bug#26468)

Retrieving rows from a table that used an index would sometimes fail to return the row. (Bug#26452)

Continue handlers in stored procedures could cause a crash. (Bug#26433)

Tables with a long multi-column index may fail to find a record for UPDATE. (Bug#26420)

Updating BLOB columns could result in a crash. (Bug#26324)

Deleting a large quantity of rows in a single table may result in ERROR 1020. (Bug#26055)

A DROP TABLE statement on a table created using CREATE TABLE ... SELECT ... crashed the server. (Bug#25564)

Random updates of LONG VARCHAR columns would fail. (Bug#23818)

Running SELECT after a changing the table contents does not result in a new data set. (Bug#22181)

Using ALTER TABLE with interleaving transactions could cause mysqld to crash. (Bug#22165)