Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
22 check-ins using file src/select.c version c620bcd0
|
2019-05-22
| ||
| 14:35 | New dbsqlfuzz find added to test/fuzzdata8.db. (check-in: 42af7c81 user: drh tags: trunk) | |
| 14:22 | Fix a buffer overread that could in fts3 when dealing with corrupt records. (check-in: 1660d773 user: dan tags: trunk) | |
|
2019-05-21
| ||
| 17:04 | Combine the implementations of the key and hexkey pragmas into a single case. Have both pragmas return "ok" if they are implemented. (check-in: b3692c40 user: drh tags: trunk) | |
| 16:32 | Fix a problem in [b5ca442a] causing an assert() to fail in REINDEX commands. (check-in: a3e77c77 user: dan tags: trunk) | |
| 14:42 | Use a statement journal for all CREATE INDEX statements in case an indexed exprsesion throws an exception when it is evaluated. Fix for [b5ca442a]. (check-in: b8071d10 user: dan tags: trunk) | |
|
2019-05-20
| ||
| 19:46 | Fix a segfault that could occur in sqlite3session_diff() if NULL were passed as the pzErrMsg argument. (check-in: aee73fd2 user: dan tags: trunk) | |
| 18:43 | Improvements to the automatic compile-time selection of byte-order, as suggested on the mailing list by Seb Kemper. (check-in: b7aad929 user: drh tags: trunk) | |
| 18:35 | A minor variation on check-in [1685610ef8e0dc] which (hopefully) makes the logic a little easier to follow. Also disallows the use of the double-quoted string hack in the query expression used for VACUUM INTO, which is not strictly required, but moves us toward the goal of disallowing the double-quoted string hack everywhere. (check-in: 3e1b55f3 user: drh tags: trunk) | |
| 17:14 | Disallow string constants enclosed in double-quotes within new CREATE TABLE and CREATE INDEX statements. It is still possible to enclose column names in double-quotes, and existing database schemas that use double-quotes for strings can still be loaded. This addresses ticket [9b78184b]. (check-in: 1685610e user: dan tags: trunk) | |
| 10:36 | Update the sqlite3ExprCompare() routine so that it does not think "? IS NOT TRUE" is the same as "? IS TRUE". Fix for [d3e7f2ba5b3]. (check-in: 99eba69b user: dan tags: trunk) | |
|
2019-05-18
| ||
| 21:22 | Fix an assert() failure that could occur in a join query if the RHS of an IN() operator is a list containing correlated expressions. This problem was introduced by checkin [e130319317e7611938] which was part of the fix for ticket [787fa716be3a7f650c] - so this commit is part of that ticket's fix too. (check-in: 778b1224 user: dan tags: trunk) | |
| 19:49 | Avoid including the comment in the output of "PRAGMA table_info" in situations where there is a comment following a DEFAULT value within a CREATE TABLE statement. (check-in: d91095ba user: dan tags: trunk) | |
|
2019-05-17
| ||
| 20:37 | Disable PRAGMA journal_mode=OFF when SQLITE_DBCONFIG_DEFENSIVE is turned on. Ticket [f4ec250930342e0c]. (check-in: a0f5eb5c user: drh tags: trunk) | |
| 15:59 | Always store a REAL value in a column with REAL affinity if the integer equivalent would require 8 bytes of storage. Fix for [3c27b97e3]. (check-in: 14c00b10 user: dan tags: trunk) | |
|
2019-05-16
| ||
| 20:40 | Add test cases to test/fuzzdata7.db for (harmless) dbfuzz2 finds. (check-in: 1eb2a628 user: drh tags: trunk) | |
| 20:36 | Initialize the 18-byte overrun area on the buffer used to reconstruct overflow btree cells during a btree search, to avoid a harmless jump-depends-on-uninit-values warning. (check-in: 4b05caeb user: drh tags: trunk) | |
| 20:13 | Fix an assert() in the OP_Delete opcode that could fail with a corrupt database. (check-in: 915388ab user: dan tags: trunk) | |
| 16:44 | Add new test file fts5corrupt4.test. (check-in: 5dfc4fe9 user: dan tags: trunk) | |
| 11:47 | Fix a harmless use-of-initialized-value fault in the assert() logic added by check-in [d612fb7873cf59d] (check-in: 3dac9072 user: drh tags: trunk) | |
| 03:47 | Fix harmless compiler warning in the session extension. (check-in: dff823ca user: mistachkin tags: trunk) | |
| 01:22 | Make sure the OP_Concat opcode always correctly zero-terminates a UTF16 string, even if the input strings are ill-formed. This is a followup to check-in [3a16ddf91f0c9c516a7] that fixes a case the previous check-in missed. Also add assert()s to prove correct zero termination. (check-in: d612fb78 user: drh tags: trunk) | |
|
2019-05-15
| ||
| 18:42 | Fix the count-of-view optimization so that it is (correctly) disabled for a query that includes a WHERE clause or a GROUP BY clause. (check-in: 05897ca4 user: drh tags: trunk) | |