Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
Comment: | Fix a typo in the lang_keywords.html page. |
---|---|
Downloads: | Tarball | ZIP archive |
Timelines: | family | ancestors | descendants | both | trunk |
Files: | files | file ages | folders |
SHA1: |
f8a77cd24f2d789530bebc55b113a99e |
User & Date: | drh 2012-02-23 12:32:45.804 |
Context
2012-02-23
| ||
14:40 | Documentation of the SQLITE_FCNTL_PRAGMA file-control. Point out that disabling compound SELECT statements also disables multi-value INSERT. (check-in: cf86dcee73 user: drh tags: trunk) | |
12:32 | Fix a typo in the lang_keywords.html page. (check-in: f8a77cd24f user: drh tags: trunk) | |
2012-02-05
| ||
05:19 | Fix an error in the FTS matchinfo documentation. (check-in: 4a7f0dacc7 user: dan tags: trunk) | |
Changes
Changes to pages/lang.in.
︙ | ︙ | |||
3610 3611 3612 3613 3614 3615 3616 | be used as the names of tables, indices, columns, databases, user-defined functions, collations, virtual table modules, or any other named object. The list of keywords is so long that few people can remember them all. For most SQL code, your safest bet is to never use any English language word as the name of a user-defined object.</p> <p>If you want to use a keyword as a name, you need to quote it. There | | | 3610 3611 3612 3613 3614 3615 3616 3617 3618 3619 3620 3621 3622 3623 3624 | be used as the names of tables, indices, columns, databases, user-defined functions, collations, virtual table modules, or any other named object. The list of keywords is so long that few people can remember them all. For most SQL code, your safest bet is to never use any English language word as the name of a user-defined object.</p> <p>If you want to use a keyword as a name, you need to quote it. There are four ways of quoting keywords in SQLite:</p> <p> <blockquote> <table> <tr> <td valign="top"><b>'keyword'</b></td><td width="20"></td> <td>^A keyword in single quotes is a string literal.</td></tr> |
︙ | ︙ |