Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Fix bugs in the compile.in webpage. Still need to update the content. |
|---|---|
| Downloads: | Tarball | ZIP archive | SQL archive |
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA1: |
2eb8090314bc17a4d32385f15c3b136f |
| User & Date: | drh 2007-11-14 03:21:56 |
Context
|
2007-11-14
| ||
| 09:11 | Update Dan's photo/biography. (check-in: 1a81556c8a user: anonymous tags: trunk) | |
| 03:21 | Fix bugs in the compile.in webpage. Still need to update the content. (check-in: 2eb8090314 user: drh tags: trunk) | |
| 03:14 | Changes capi3ref.html references to c3ref/ pages everywhere. (check-in: c3a14fe2c7 user: drh tags: trunk) | |
Changes
Changes to pages/compile.in.
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
...
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
|
"PRAGMA auto_vacuum" statement is not an error, but does not return a value or modify the auto-vacuum flag in the database file. If a database that supports auto-vacuum is opened by a library compiled with this option, it is automatically opened in read-only mode. </p> <p><b>SQLITE_OMIT_AUTOINCREMENT</b><br> This option is used to omit the AUTOINCREMENT functionality. When this is macro is defined, columns declared as "INTEGER PRIMARY KEY AUTOINCREMENT" behave in the same way as columns declared as "INTEGER PRIMARY KEY" when a NULL is inserted. The sqlite_sequence system table is neither created, nor respected if it already exists. </p> <p><i>TODO: Need a link here - AUTOINCREMENT is not yet documented</i><p> <p><b>SQLITE_OMIT_BLOB_LITERAL</b><br> When this option is defined, it is not possible to specify a blob in an SQL statement using the X'ABCD' syntax.</p> } #<p>WARNING: The VACUUM command depends on this syntax for vacuuming databases #that contain blobs, so disabling this functionality may render a database #unvacuumable. #</p> #<p><i>TODO: Need a link here - is that syntax documented anywhere?</i><p> puts { <p><b>SQLITE_OMIT_COMPLETE</b><br> This option causes the <a href="c3ref/complete.html"> sqlite3_complete</a> API to be omitted. </p> <p><b>SQLITE_OMIT_COMPOUND_SELECT</b><br> ................................................................................ Defining this option omits pragmas for querying and modifying the database schema version and user version from the build. Specifically, the <a href="pragma.html#pragma_schema_version">schema_version</a> and <a href="pragma.html#pragma_user_version">user_version</a> pragmas are omitted. <p><b>SQLITE_OMIT_SUBQUERY</b><br> <p>If defined, support for sub-selects and the IN() operator are omitted. </p> <p><b>SQLITE_OMIT_TCL_VARIABLE</b><br> <p>If this macro is defined, then the special "$<variable-name>" syntax used to automatically bind SQL variables to TCL variables is omitted. </p> <p><b>SQLITE_OMIT_TRIGGER</b><br> Defining this option omits support for VIEW objects. Neither the <a href="lang_createtrigger.html">CREATE TRIGGER</a> or <a href="lang_droptrigger.html">DROP TRIGGER</a> |
|
>
<
<
<
<
<
<
<
<
|
|
|
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
...
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
|
"PRAGMA auto_vacuum" statement is not an error, but does not return a value or modify the auto-vacuum flag in the database file. If a database that supports auto-vacuum is opened by a library compiled with this option, it is automatically opened in read-only mode. </p> <p><b>SQLITE_OMIT_AUTOINCREMENT</b><br> This option is used to omit the <a href="autoinc.html">AUTOINCREMENT</a> functionality. When this is macro is defined, columns declared as "INTEGER PRIMARY KEY AUTOINCREMENT" behave in the same way as columns declared as "INTEGER PRIMARY KEY" when a NULL is inserted. The sqlite_sequence system table is neither created, nor respected if it already exists. </p> <p><b>SQLITE_OMIT_BLOB_LITERAL</b><br> When this option is defined, it is not possible to specify a blob in an SQL statement using the X'ABCD' syntax.</p> <p><b>SQLITE_OMIT_COMPLETE</b><br> This option causes the <a href="c3ref/complete.html"> sqlite3_complete</a> API to be omitted. </p> <p><b>SQLITE_OMIT_COMPOUND_SELECT</b><br> ................................................................................ Defining this option omits pragmas for querying and modifying the database schema version and user version from the build. Specifically, the <a href="pragma.html#pragma_schema_version">schema_version</a> and <a href="pragma.html#pragma_user_version">user_version</a> pragmas are omitted. <p><b>SQLITE_OMIT_SUBQUERY</b><br> If defined, support for sub-selects and the IN() operator are omitted. </p> <p><b>SQLITE_OMIT_TCL_VARIABLE</b><br> If this macro is defined, then the special "$<variable-name>" syntax used to automatically bind SQL variables to TCL variables is omitted. </p> <p><b>SQLITE_OMIT_TRIGGER</b><br> Defining this option omits support for VIEW objects. Neither the <a href="lang_createtrigger.html">CREATE TRIGGER</a> or <a href="lang_droptrigger.html">DROP TRIGGER</a> |