Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Fix typo in the pointer-passing document. |
|---|---|
| Downloads: | Tarball | ZIP archive |
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA3-256: |
2de67f2a1aec21e225750882b62308a8 |
| User & Date: | drh 2017-08-03 14:18:30.103 |
Context
|
2017-08-03
| ||
| 14:35 | Amplify one of the points justifying static string pointer types. (check-in: 6604546bb4 user: drh tags: trunk) | |
| 14:18 | Fix typo in the pointer-passing document. (check-in: 2de67f2a1a user: drh tags: trunk) | |
| 13:02 | Increased detail on pointer types in the bindptr.html document. (check-in: 1316d197a4 user: drh tags: trunk) | |
Changes
Changes to pages/bindptr.in.
| ︙ | ︙ | |||
367 368 369 370 371 372 373 | <p> If ownership of the pointer is passed into SQLite by providing a non-NULL D parameter to [sqlite3_bind_pointer()] or [sqlite3_result_pointer()] then the ownership remains with SQLite until the object is destroyed. There is no way to transfer ownership out of SQLite and back into the application again. | < < < | 367 368 369 370 371 372 373 374 375 376 377 378 379 380 | <p> If ownership of the pointer is passed into SQLite by providing a non-NULL D parameter to [sqlite3_bind_pointer()] or [sqlite3_result_pointer()] then the ownership remains with SQLite until the object is destroyed. There is no way to transfer ownership out of SQLite and back into the application again. <h1>Restrictions On The Use of Pointer Values</h1> <p> The pointers that piggy-back on SQL NULL values using the [sqlite3_bind_pointer()], [sqlite3_result_pointer()], and [sqlite3_value_pointer()] interface are transient and ephemeral. The pointers are never written into the database. The pointers |
| ︙ | ︙ |