Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
Comment: | Fix typo in the generated columns description. |
---|---|
Downloads: | Tarball | ZIP archive |
Timelines: | family | ancestors | descendants | both | trunk |
Files: | files | file ages | folders |
SHA3-256: |
eaa1cd343ff97ed3769ebe79d6e1667a |
User & Date: | drh 2019-10-29 09:03:49.433 |
Context
2019-10-29
| ||
16:31 | Updates to the generated column documentation. Notate that the legacy_file_format pragma has been removed and replaced by the SQLITE_DBCONFIG_LEGACY_FILE_FORMAT option to sqlite3_db_config(). (check-in: 4b80493d37 user: drh tags: trunk) | |
09:03 | Fix typo in the generated columns description. (check-in: eaa1cd343f user: drh tags: trunk) | |
03:35 | Tighten the requirement so that every table must have at least one non-generated column. A STORED column does not count. (check-in: 3103f83e9e user: drh tags: trunk) | |
Changes
Changes to pages/gencol.in.
︙ | ︙ | |||
57 58 59 60 61 62 63 | in the database file, whereas VIRTUAL columns use more CPU cycles when being read. <p>From the point of view of SQL, STORED and VIRTUAL columns are almost exactly the same. Queries against either class of generated column produce the same results. The only functional difference is that one cannot add new STORED columns using the | | | 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 | in the database file, whereas VIRTUAL columns use more CPU cycles when being read. <p>From the point of view of SQL, STORED and VIRTUAL columns are almost exactly the same. Queries against either class of generated column produce the same results. The only functional difference is that one cannot add new STORED columns using the [ALTER TABLE ADD COLUMN] command. Only VIRTUAL columns can be added using ALTER TABLE. <h2>Restrictions And Limitations</h2> <ol> <li><p> Generated columns may not have a [default value] (they may not use the |
︙ | ︙ |