Documentation Source Text

Check-in [78d484e889]
Login

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview
Comment:Fix a detail of the case_sensitive_like pragma documentation to more accurately describe what really happens.
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA1: 78d484e8892fdd9b4f8f010f6ef2e14b4e89864d
User & Date: drh 2010-12-16 17:19:55
Context
2010-12-16
17:20
Add documentation of the SQLITE_DEFAULT_FOREIGN_KEY compile-time parameter. check-in: d606802b48 user: drh tags: trunk
17:19
Fix a detail of the case_sensitive_like pragma documentation to more accurately describe what really happens. check-in: 78d484e889 user: drh tags: trunk
2010-12-09
18:56
Add documentation for the SQLITE_DEFAULT_WAL_AUTOCHECKPOINT compile-time option. Other updates to PRAGMA documentation. check-in: 140df585c3 user: drh tags: trunk
Changes
Hide Diffs Unified Diffs Ignore Whitespace Patch

Changes to pages/pragma.in.

209
210
211
212
213
214
215
216
217

218
219
220
221
222
223
224
225
226
...
334
335
336
337
338
339
340


341
342
343
344
345
346
347
348
    LIKE function that is either case sensitive or insensitive depending
    on the value of the case_sensitive_like pragma.
    ^When case_sensitive_like is disabled, the default LIKE behavior is
    expressed.  ^(When case_sensitive_like is enabled, case becomes
    significant.  So, for example,
    <b>'a' LIKE 'A'</b> is false but <b>'a' LIKE 'a'</b> is still true.)^</p>

    <p>^Each invocation of this pragma causes any application-defined
    LIKE and/or GLOB functions created using the [sqlite3_create_function()]

    family of interfaces to be replaced with the built-in LIKE and GLOB
    implementations.</p>
}

Pragma checkpoint_fullfsync {
    <p>^(<b>PRAGMA checkpoint_fullfsync
       <br>PRAGMA checkpoint_fullfsync = </b><i>boolean</i><b>;</b></p>
    <p>Query or change the fullfsync flag for [checkpoint] operations.)^
    ^If this flag is set, then the F_FULLFSYNC syncing method is used
................................................................................
       using the database connection, including those prepared before the
       setting was changed. ^Any existing statements prepared using the legacy 
       [sqlite3_prepare()] interface may fail with an [SQLITE_SCHEMA] error
       after the foreign_keys setting is changed.

    <p>^(As of SQLite [version 3.6.19], the default setting for foreign
       key enforcement is OFF.)^  However, that might change in a future


       release of SQLite.  To minimize future problems, applications should
       set the foreign key enforcement flag as required by the application
       and not depend on the default setting.
}


LegacyPragma full_column_names {
    <p><b>PRAGMA full_column_names;







<
|
>
|
<







 







>
>
|







209
210
211
212
213
214
215

216
217
218

219
220
221
222
223
224
225
...
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
    LIKE function that is either case sensitive or insensitive depending
    on the value of the case_sensitive_like pragma.
    ^When case_sensitive_like is disabled, the default LIKE behavior is
    expressed.  ^(When case_sensitive_like is enabled, case becomes
    significant.  So, for example,
    <b>'a' LIKE 'A'</b> is false but <b>'a' LIKE 'a'</b> is still true.)^</p>


    <p>^This pragma uses [sqlite3_create_function()] to overload the
    LIKE and GLOB functions, which may override previous implementations
    of LIKE and GLOB registered by the application.</p>

}

Pragma checkpoint_fullfsync {
    <p>^(<b>PRAGMA checkpoint_fullfsync
       <br>PRAGMA checkpoint_fullfsync = </b><i>boolean</i><b>;</b></p>
    <p>Query or change the fullfsync flag for [checkpoint] operations.)^
    ^If this flag is set, then the F_FULLFSYNC syncing method is used
................................................................................
       using the database connection, including those prepared before the
       setting was changed. ^Any existing statements prepared using the legacy 
       [sqlite3_prepare()] interface may fail with an [SQLITE_SCHEMA] error
       after the foreign_keys setting is changed.

    <p>^(As of SQLite [version 3.6.19], the default setting for foreign
       key enforcement is OFF.)^  However, that might change in a future
       release of SQLite.  The default setting for foreign key enforcement
       can be specified at compile-time using the [SQLITE_DEFAULT_FOREIGN_KEYS]
       preprocessor macro.  To minimize future problems, applications should
       set the foreign key enforcement flag as required by the application
       and not depend on the default setting.
}


LegacyPragma full_column_names {
    <p><b>PRAGMA full_column_names;