2019-04-19
| ||
18:23 | • Fixed ticket [f00d7b651a]: ALTER TABLE corrupts the schema for tables that start with "sqlite" plus 5 other changes (artifact: c58968e526 user: drh) | |
16:34 | Fix a problem with renaming a table that starts with "sqlite". Fix for ticket [f00d7b65]. (check-in: a2ead8aa45 user: dan tags: trunk) | |
16:26 | • New ticket [f00d7b651a] ALTER TABLE corrupts the schema for tables that start with "sqlite". (artifact: dacc8af23a user: drh) | |
Ticket Hash: | f00d7b651aa3cc3ee5df12e84b83b4bd96ee4524 | ||
Title: | ALTER TABLE corrupts the schema for tables that start with "sqlite" | ||
Status: | Fixed | Type: | Code_Defect |
Severity: | Severe | Priority: | Immediate |
Subsystem: | Unknown | Resolution: | Fixed |
Last Modified: |
2019-04-19 18:23:36 6.21 years ago |
Created: |
2019-04-19 16:26:26 6.21 years ago |
Version Found In: | 3.28.0 |
User Comments: | ||||
drh added on 2019-04-19 16:26:26:
The following sequence of SQL statements results in an sqlite_master table that has one name for the table in the "name" column but a different name in the "sql" column: CREATE TABLE "sqlite1234" ("id" integer); ALTER TABLE "sqlite1234" RENAME TO "User"; SELECT name, sql FROM sqlite_master WHERE sql IS NOT NULL; This issue was reported on the mailing list by Semih Hazar. The problem appears to have originated in SQLite version 3.25.0. |