LIMIT clause on sub-select in FROM clause of a SELECT in a UNION ALL interpreted incorrectly

OFFSET ignored if there is no FROM clause

Incorrect result when an index is used for an ordered join

COLLATE issue in a view

Assertion fault on a query against a view

Assertion

MAX yields unexpected result for UTF-16

Incorrect query result when redundant terms appears in WHERE clause

Segfault when running query that uses SUM()OVER()

Query "<A> left join <B> inner join <C> on <b_c_expr> on <a_b_expr>" caused left join behave like inner join.

Incorrect result from LEFT JOIN with a subquery on the LHS

OR operator in WHERE clause gives wrong answer when indexed

Incorrect results with OR terms in the ON clause of a LEFT JOIN

Incorrect DISTINCT on an indexed query with IN

Inaccurate int/float comparison results in corrupt index

Some valid floating-point literals are not recognized.

REAL rounding seems to depend on index presence

MIN() malfunctions for UNIQUE column

Segfault

Assertion when "WHERE 0" on the first element of a UNION present

Crash on query using an OR term in the WHERE clause

Crash due to misuse of window functions.

Incorrect caching of sub-query results in the FROM clause of a scalar sub-query.

Wrong result of COUNT when using WHERE clause with POSITION()

Correlated subquery on the RHS of an IN operator causes output of excessive rows

Incorrect ORDER BY on an indexed JOIN

Incorrect result for LEFT JOIN

Incorrect output on a LEFT JOIN

Assertion fault when multi-use subquery implemented by co-routine

Segfault when running query that has WHERE expression with IN(...) containing LEAD()OVER() function

Segfault following heavy SAVEPOINT usage

INSERT into table with two triggers does not terminate

Bug involving subqueries and the OR optimization

ALTER TABLE ADD COLUMN with negative DEFAULT value

Incorrect query result when a LEFT JOIN subquery is flattened

Incorrect result with ORDER BY DESC and LIMIT

Scalar subquery with "LIMIT 0" should return NULL

Assertion

Incorrect output order on a join with an ORDER BY

BETWEEN issue in a view

LEFT JOIN in view malfunctions

Segfault while trying to prepare a malformed window-function query

LIKE malfunctions for INT PRIMARY KEY COLLATE NOCASE column

Assertion in UPDATE statement for textual column which has check constraint that involves numeric comparison

Incorrect LIMIT on a UNION ALL query

Incorrect result from LEFT JOIN with OR in the WHERE clause

Incorrect result on LEFT JOIN with OR constraints and an ORDER BY clause

RENAME COLUMN fails on tables with redundant UNIQUE constraints

Segfault during query involving LEFT JOIN column in the ORDER BY clause

Incorrect LIKE result

Segfault on query involving deeply nested aggregate views

Incorrect result from WITH RECURSIVE using DISTINCT

Incorrect result on query involving LEFT JOIN and transitive constraints

ALTER TABLE DROP <column> may corrupt data

ORDER BY clause ignored in 3-way join query

Segfault due to LEFT JOIN flattening optimization

NULL WHERE condition unexpectedly results in row being fetched

Duplicate CTE name gives incorrect result

LEFT JOIN with an OR in the ON clause causes segfault

Query planner fault on three-way nested join with compound inner SELECT

COLLATE operator on lhs of BETWEEN expression is ignored.

SELECT on window function FIRST_VALUE()OVER() causes a segfault

Incorrect result when RHS of IN operator contains DISTINCT and LIMIT

Foreign key constraint fails to prevent consistency error.

Assertion

COLLATE in BETWEEN expression is ignored

Incorrect result using index on expression with collating function

Incorrect result with complex OR-connected WHERE

Assertion fault when window functions are used.

Incorrect ORDER BY with colliding input and output column names

Segfault when running query that uses window functions

Incorrect result for query that uses MIN() and a CAST on rowid

Incorrect sorting when a column uses BINARY collation in the ORDER BY, but is compared with a different collation in the WHERE clause

Assertion in the query containing subquery in select section and exists()

LIMIT clause on sub-select in FROM clause of a SELECT in a UNION ALL interpreted incorrectly

LIMIT clause on sub-select in FROM clause of a SELECT in a UNION ALL interpreted incorrectly

OFFSET ignored if there is no FROM clause

OFFSET ignored if there is no FROM clause

Incorrect result when an index is used for an ordered join

Incorrect result when an index is used for an ordered join

COLLATE issue in a view