Opened 9 years ago
Last modified 6 years ago
#779 new enhancement
Update tables created without "INTEGER PRIMARY KEY"
| Reported by: | dstillman | Owned by: | dstillman |
|---|---|---|---|
| Priority: | minor | Milestone: | |
| Component: | data layer | Version: | 1.5 |
| Keywords: | Cc: |
Description
For clarity, I wasn't using "INTEGER PRIMARY KEY" in tables that weren't using autoincrement functionality, but not using it keeps SQLite from just making that column name an alias for the internal rowid column--in other words, it creates an extra row.
May want to do this gradually to avoid large migrations.
Change History (2)
comment:1 Changed 9 years ago by dstillman
comment:2 Changed 6 years ago by dstillman
- Milestone 2.0 Beta 3 deleted
Milestone 2.0 Beta 3 deleted
Note: See
TracTickets for help on using
tickets.
(In [1738]) Updated schema to use "INTEGER PRIMARY KEY" for all applicable rows -- for clarity, I wasn't using it for tables that weren't using autoincrement functionality, but not using it keeps SQLite from just making that column name an alias for the internal rowid column, resulting in an extra unnecessary column. Can't update existing tables now, but may in 1.5. (Refs #779, Update tables created without "INTEGER PRIMARY KEY")