Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Fix a typo in loadext.html. |
|---|---|
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA3-256: | 4efb429d19a753f4b650febbd8e1dc65 |
| User & Date: | drh 2019-02-12 13:54:59 |
Context
|
2019-02-15
| ||
| 11:43 | Fix a typo in the ALTER TABLE documentation. check-in: 625c9fbdad user: drh tags: trunk | |
|
2019-02-12
| ||
| 13:54 | Fix a typo in loadext.html. check-in: 4efb429d19 user: drh tags: trunk | |
| 12:27 | Clarify how the SQLITE_OK_LOAD_PERMANENTLY return value should be used. check-in: 8182293dd8 user: drh tags: trunk | |
Changes
Changes to pages/loadext.in.
267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 |
not be unloaded (xDlClose will not be invoked) and the extension will remain in process memory indefinitely. The SQLITE_OK_LOAD_PERMANENTLY return value is useful for extensions that want to register new [VFSes]. <p>To clarify: an extension for which the initialization function returns SQLITE_OK_LOAD_PERMANENTLY continues to exist in memory after the database connection closes. However, the extension is <em>not</em> automatically registered with subsequent database connections. This make it possible to load extensions that implement new [VFSes]. To persistently load and register an extension that implements new SQL functions, collating sequences, and/or virtual tables, such that those added capabilities are available to all subsequent database connections, then the initialization routine should also invoke [sqlite3_auto_extension()] on a subfunction that will register those services. |
| |
267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 |
not be unloaded (xDlClose will not be invoked) and the extension will remain
in process memory indefinitely. The SQLITE_OK_LOAD_PERMANENTLY return
value is useful for extensions that want to register new [VFSes].
<p>To clarify: an extension for which the initialization function returns
SQLITE_OK_LOAD_PERMANENTLY continues to exist in memory after the database
connection closes. However, the extension is <em>not</em> automatically
registered with subsequent database connections. This makes it possible
to load extensions that implement new [VFSes].
To persistently load and register an extension that implements new SQL
functions, collating sequences, and/or virtual tables, such that those
added capabilities are available to all subsequent database connections,
then the initialization routine should also invoke [sqlite3_auto_extension()]
on a subfunction that will register those services.
|