|
2019-10-29
| ||
| 16:19 | • Fixed ticket [6484e6ce]: VACUUM on table with generated column results in an error plus 6 other changes (artifact: 56f2a7d5 user: drh) | |
| 16:18 | Remove the legacy_file_format PRAGMA. In its place, provide the SQLITE_DBCONFIG_LEGACY_FILE_FORMAT option to sqlite3_db_config(). Fix for ticket [6484e6ce678fffab] (check-in: 4d424f30 user: drh tags: trunk) | |
| 09:24 | • New ticket [6484e6ce] VACUUM on table with generated column results in an error. (artifact: d41ad93d user: mrigger) | |
| Ticket Hash: | 6484e6ce678fffab6371cddc2e7e530ac4d8fd72 | |||
| Title: | VACUUM on table with generated column results in an error | |||
| Status: | Fixed | Type: | Code_Defect | |
| Severity: | Minor | Priority: | Immediate | |
| Subsystem: | Unknown | Resolution: | Fixed | |
| Last Modified: | 2019-10-29 16:19:00 | |||
| Version Found In: | 3.30.0 | |||
| User Comments: | ||||
|
mrigger added on 2019-10-29 09:24:24:
Consider the following test case: CREATE TABLE t0(c0 AS(1), c1); PRAGMA legacy_file_format = true; CREATE INDEX i0 ON t0(0 DESC); VACUUM; -- table vacuum_db.t0 has 1 columns but 2 values were supplied Unexpectedly, the VACUUM statement results in an error. This issue seems to be closely related to [166347c6fc]. | ||||