Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
Comment: | Update the change log. Fix typo in virtual table documentation. |
---|---|
Downloads: | Tarball | ZIP archive |
Timelines: | family | ancestors | descendants | both | trunk |
Files: | files | file ages | folders |
SHA3-256: |
32c5dad1b29a14d1931b673b927fb06f |
User & Date: | drh 2018-04-30 22:27:05.720 |
Context
2018-05-04
| ||
02:36 | Begin revising the EXPLAIN QUERY PLAN document. More work is needed here. Update the change log. (check-in: f07b7a3a18 user: drh tags: trunk) | |
2018-04-30
| ||
22:27 | Update the change log. Fix typo in virtual table documentation. (check-in: 32c5dad1b2 user: drh tags: trunk) | |
2018-04-25
| ||
00:02 | Updates to the change log. (check-in: 6d211fe371 user: drh tags: trunk) | |
Changes
Changes to pages/changes.in.
︙ | ︙ | |||
19 20 21 22 23 24 25 26 27 28 29 30 31 32 | set aChng($nChng) [list $date $desc $options] set xrefChng($date) $nChng incr nChng } chng {2018-07-00 (3.24.0)} { <li> Add support for PostgreSQL-style [UPSERT]. <li> Enhance [ALTER TABLE] so that it recognizes "true" and "false" as valid arguments to DEFAULT. <li> Added the sorter-reference optimization as a compile-time option. Only available if compiled with SQLITE_ENABLE_SORTER_REFERENCES. <li> The [CLI] automatically intercepts the raw [EXPLAIN QUERY PLAN] output an reformats it into an ASCII-art graph. <li> Enhance the query planner to allow the [OR optimization] to proceed | > > > | 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 | set aChng($nChng) [list $date $desc $options] set xrefChng($date) $nChng incr nChng } chng {2018-07-00 (3.24.0)} { <li> Add support for PostgreSQL-style [UPSERT]. <li> Added new C-language APIs for discovering SQL keywords used by SQLite: [sqlite3_keyword_count()], [sqlite3_keyword_name()], and [sqlite3_keyword_check()]. <li> Enhance [ALTER TABLE] so that it recognizes "true" and "false" as valid arguments to DEFAULT. <li> Added the sorter-reference optimization as a compile-time option. Only available if compiled with SQLITE_ENABLE_SORTER_REFERENCES. <li> The [CLI] automatically intercepts the raw [EXPLAIN QUERY PLAN] output an reformats it into an ASCII-art graph. <li> Enhance the query planner to allow the [OR optimization] to proceed |
︙ | ︙ |
Changes to pages/vtab.in.
︙ | ︙ | |||
1119 1120 1121 1122 1123 1124 1125 | must choose a rowid for the newly inserted row. Subsequent argv[] entries contain values of the columns of the virtual table, in the order that the columns were declared. The number of columns will match the table declaration that the [xConnect] or [xCreate] method made using the [sqlite3_declare_vtab()] call. All hidden columns are included. <p>When doing an insert without a rowid (argc>1, argv[1] is an SQL NULL), | | | 1119 1120 1121 1122 1123 1124 1125 1126 1127 1128 1129 1130 1131 1132 1133 | must choose a rowid for the newly inserted row. Subsequent argv[] entries contain values of the columns of the virtual table, in the order that the columns were declared. The number of columns will match the table declaration that the [xConnect] or [xCreate] method made using the [sqlite3_declare_vtab()] call. All hidden columns are included. <p>When doing an insert without a rowid (argc>1, argv[1] is an SQL NULL), on a virtual table that uses ROWID (but not on a [WITHOUT ROWID virtual table]), the implementation must set *pRowid to the rowid of the newly inserted row; this will become the value returned by the [sqlite3_last_insert_rowid()] function. Setting this value in all the other cases is a harmless no-op; the SQLite engine ignores the *pRowid return value if argc==1 or argv[1] is not an SQL NULL. <p>Each call to xUpdate will fall into one of cases shown below. |
︙ | ︙ |