Documentation Source Text

Check-in [84ce96a21d]
Login

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

Overview
Comment:Fix typo identified by cvstrac ticket #3136.
Downloads: Tarball | ZIP archive
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA1: 84ce96a21d713d69189c3c21cfde538d005e5c85
User & Date: dan 2008-06-23 11:16:21.000
Context
2008-06-25
06:35
Typo, fixes #3170. (check-in: 67eb1e7a66 user: mihailim tags: trunk)
2008-06-23
11:16
Fix typo identified by cvstrac ticket #3136. (check-in: 84ce96a21d user: dan tags: trunk)
2008-06-18
13:49
Fix a broken link int the custombuild.html page. Sort the list of objects on the c3ref/objlist.html page. (check-in: 0466a1ef20 user: drh tags: trunk)
Changes
Unified Diff Ignore Whitespace Patch
Changes to pages/cintro.in.
︙︙
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274


<p>
  The [sqlite3_exec()] interface is a convenience wrapper that carries out
  all four of the above steps with a single function call.  A callback
  function passed into [sqlite3_exec()] is used to process each row of
  the result set.  The [sqlite3_get_table()] is another convenience wrapper
  that does all four of the above steps.  The [sqlite3_get_table()] interface
  differs from [sqlite3_get_table()] in that it stores the results of queries
  in heap memory rather than invoking a callback.
</p>

<p>
  It is important to realize that neither [sqlite3_exec()] nor
  [sqlite3_get_table()] do anything that cannot be accomplished using
  the core routines.  In fact, these wrappers are implemented purely in








|








260
261
262
263
264
265
266
267
268
269
270
271
272
273
274


<p>
  The [sqlite3_exec()] interface is a convenience wrapper that carries out
  all four of the above steps with a single function call.  A callback
  function passed into [sqlite3_exec()] is used to process each row of
  the result set.  The [sqlite3_get_table()] is another convenience wrapper
  that does all four of the above steps.  The [sqlite3_get_table()] interface
  differs from [sqlite3_exec()] in that it stores the results of queries
  in heap memory rather than invoking a callback.
</p>

<p>
  It is important to realize that neither [sqlite3_exec()] nor
  [sqlite3_get_table()] do anything that cannot be accomplished using
  the core routines.  In fact, these wrappers are implemented purely in
︙︙