Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
Comment: | Make it clear in the docs that virtual tables and shared cache do not play well together. (CVS 3846) |
---|---|
Downloads: | Tarball | ZIP archive |
Timelines: | family | ancestors | descendants | both | trunk |
Files: | files | file ages | folders |
SHA1: |
62ef2b1127e76eae0f76ac51f8238446 |
User & Date: | drh 2007-04-16 15:35:24.000 |
Context
2007-04-16
| ||
15:49 | Add test cases to make sure virtual tables cannot be used in shared-cache mode. (CVS 3847) (check-in: 66e468adfc user: danielk1977 tags: trunk) | |
15:35 | Make it clear in the docs that virtual tables and shared cache do not play well together. (CVS 3846) (check-in: 62ef2b1127 user: drh tags: trunk) | |
15:06 | Ensure sqlite3_finalize() can be called from within the xDisconnect() method of virtual tables. (CVS 3845) (check-in: 8d6c3bfc4d user: danielk1977 tags: trunk) | |
Changes
Changes to www/capi3ref.tcl.
|
| | | 1 2 3 4 5 6 7 8 | set rcsid {$Id: capi3ref.tcl,v 1.55 2007/04/16 15:35:24 drh Exp $} source common.tcl header {C/C++ Interface For SQLite Version 3} puts { <h2 class=pdf_section>C/C++ Interface For SQLite Version 3</h2> } proc api {name prototype desc {notused x}} { |
︙ | ︙ | |||
1634 1635 1636 1637 1638 1639 1640 1641 1642 1643 1644 1645 1646 1647 | When the shared cache is enabled, the following routines must always be called from the same thread: sqlite3_open(), sqlite3_prepare_v2(), sqlite3_step(), sqlite3_reset(), sqlite3_finalize(), and sqlite3_close(). This is due to the fact that the shared cache makes use of thread-specific storage so that it will be available for sharing with other connections. This routine returns SQLITE_OK if shared cache was enabled or disabled successfully. An error code is returned otherwise. Shared cache is disabled by default for backward compatibility. } | > > > > | 1634 1635 1636 1637 1638 1639 1640 1641 1642 1643 1644 1645 1646 1647 1648 1649 1650 1651 | When the shared cache is enabled, the following routines must always be called from the same thread: sqlite3_open(), sqlite3_prepare_v2(), sqlite3_step(), sqlite3_reset(), sqlite3_finalize(), and sqlite3_close(). This is due to the fact that the shared cache makes use of thread-specific storage so that it will be available for sharing with other connections. Virtual tables cannot be used with a shared cache. When shared cache is enabled, the sqlite3_create_module() API used to register virtual tables will always return an error. This routine returns SQLITE_OK if shared cache was enabled or disabled successfully. An error code is returned otherwise. Shared cache is disabled by default for backward compatibility. } |
︙ | ︙ |