Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
Comment: | Fix a long-standing typo in the ALTER TABLE documentation. |
---|---|
Downloads: | Tarball | ZIP archive |
Timelines: | family | ancestors | descendants | both | trunk |
Files: | files | file ages | folders |
SHA3-256: |
9b5947f2ee88d9c5c67c2120276dc29f |
User & Date: | drh 2018-09-06 20:36:53.653 |
Context
2018-09-06
| ||
21:37 | Improvements to the RENAME COLUMN syntax diagram. (check-in: c951c8c482 user: drh tags: trunk) | |
20:36 | Fix a long-standing typo in the ALTER TABLE documentation. (check-in: 9b5947f2ee user: drh tags: trunk) | |
20:34 | Update the documentation to reflect the enhancements to ALTER TABLE. (check-in: c3c04a7bb4 user: drh tags: trunk) | |
Changes
Changes to pages/lang.in.
︙ | ︙ | |||
275 276 277 278 279 280 281 | <li><p> If the change to table X also affects other tables or indexes or triggers are views within schema, then run [UPDATE] statements to modify those other tables indexes and views too. For example, if the name of a column changes, all FOREIGN KEY constraints, triggers, indexes, and views that refer to that column must be modified. <p><em>Caution:</em> Once again, making changes to the sqlite_master table like this will render the database corrupt and unreadable if the | | | 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 | <li><p> If the change to table X also affects other tables or indexes or triggers are views within schema, then run [UPDATE] statements to modify those other tables indexes and views too. For example, if the name of a column changes, all FOREIGN KEY constraints, triggers, indexes, and views that refer to that column must be modified. <p><em>Caution:</em> Once again, making changes to the sqlite_master table like this will render the database corrupt and unreadable if the change contains an error. Carefully test this entire procedure on a separate test database prior to using it on a database containing important data and/or make backup copies of important databases prior to running this procedure. <li><p> Increment the schema version number using [PRAGMA schema_version | PRAGMA schema_version=X] where X is one more than the old schema version number found in step 2 above. |
︙ | ︙ |