Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Fix typos in the documentation of xDisconnect and xDestroy methods of virtual tables. |
|---|---|
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA1: |
1974081af3c880e36f3410e4a0654774 |
| User & Date: | drh 2012-10-29 19:14:55 |
Context
|
2012-10-30
| ||
| 18:15 | Import the download page changes from the 3.7.14 branch. check-in: 1bbb35f908 user: drh tags: trunk | |
|
2012-10-29
| ||
| 19:14 | Fix typos in the documentation of xDisconnect and xDestroy methods of virtual tables. check-in: 1974081af3 user: drh tags: trunk | |
| 13:15 | Fix the name of the command-line tool in the whentouse.html page. check-in: bb4847adbb user: drh tags: trunk | |
Changes
Changes to pages/vtab.in.
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
...
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
|
This method undoes the work of [xConnect]. <p>This method is a destructor for a connection to the virtual table. Contrast this method with [xDestroy]. The xDestroy is a destructor for the entire virtual table. <p>The xDestroy method is required for every virtual table implementation, though it is acceptable for the [xDisconnect] and xDestroy methods to be the same function if that makes sense for the particular virtual table. <tcl>########################################################## xDestroy hd_fragment {sqlite3_module.xDestroy} {xDestroy}</tcl> <h3>2.5 The xDestroy Method</h3> <blockquote><pre> ................................................................................ the [xDisconnect] method, and it also destroys the underlying table implementation. This method undoes the work of [xCreate]. <p>The [xDisconnect] method is called whenever a database connection that uses a virtual table is closed. The xDestroy method is only called when a [DROP TABLE] statement is executed against the virtual table. <p>The xDisconnect method is required for every virtual table implementation, though it is acceptable for the xDisconnect and [xDestroy] methods to be the same function if that makes sense for the particular virtual table. <tcl>########################################################## xOpen hd_fragment xopen {sqlite3_module.xOpen}</tcl> <h3>2.6 The xOpen Method</h3> <blockquote><pre> |
|
|
|
|
|
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
...
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
|
This method undoes the work of [xConnect]. <p>This method is a destructor for a connection to the virtual table. Contrast this method with [xDestroy]. The xDestroy is a destructor for the entire virtual table. <p>The xDisconnect method is required for every virtual table implementation, though it is acceptable for the xDisconnect and [xDestroy] methods to be the same function if that makes sense for the particular virtual table. <tcl>########################################################## xDestroy hd_fragment {sqlite3_module.xDestroy} {xDestroy}</tcl> <h3>2.5 The xDestroy Method</h3> <blockquote><pre> ................................................................................ the [xDisconnect] method, and it also destroys the underlying table implementation. This method undoes the work of [xCreate]. <p>The [xDisconnect] method is called whenever a database connection that uses a virtual table is closed. The xDestroy method is only called when a [DROP TABLE] statement is executed against the virtual table. <p>The xDestroy method is required for every virtual table implementation, though it is acceptable for the [xDisconnect] and xDestroy methods to be the same function if that makes sense for the particular virtual table. <tcl>########################################################## xOpen hd_fragment xopen {sqlite3_module.xOpen}</tcl> <h3>2.6 The xOpen Method</h3> <blockquote><pre> |