Documentation Source Text

Check-in [1bac33959e]
Login

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

Overview
Comment:Fix typos and clarify text in the sessionintro.html document.
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA3-256: 1bac33959e413438c875f56bd70e27221f668d67eaed74466286588f012e56eb
User & Date: drh 2017-03-31 15:40:14
Context
2017-04-08
11:38
Clarify what it means when it says "JSON1 is not available by default." check-in: 16bd995f65 user: drh tags: trunk
2017-03-31
15:40
Fix typos and clarify text in the sessionintro.html document. check-in: 1bac33959e user: drh tags: trunk
2017-03-30
16:43
Add documentation for the unlock_notify method of the TCL interface. check-in: d6dd485d18 user: drh tags: trunk
Changes
Hide Diffs Unified Diffs Ignore Whitespace Patch

Changes to pages/sessionintro.in.

276
277
278
279
280
281
282
283
284
285
286

287
288

289
290
291
292
293
294
295

  <li> <p> The session object is deleted using a call to the 
           [sqlite3session_delete()] API function.

       <p> It is not necessary to delete a session object after extracting
           a changeset or patchset from it. It can be left attached to the
           database handle and will continue monitoring for changes on the
           configured tables as before. However, not that if 
           [sqlite3session_changeset()] or [sqlite3session_patchset()] is
           called a second time on a session ojbect the changeset or patchset
           still reflects all changes that have taken place on the connection

           since the session was created. A session object is not reset or
           zeroed by a call to sqlite3session_changeset() or patchset().

</ol>

<codeblock class=C>
  /*
  ** Argument zSql points to a buffer containing an SQL script to execute 
  ** against the database handle passed as the first argument. As well as
  ** executing the SQL script, this function collects a changeset recording







|

|
|
>
|
|
>







276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297

  <li> <p> The session object is deleted using a call to the 
           [sqlite3session_delete()] API function.

       <p> It is not necessary to delete a session object after extracting
           a changeset or patchset from it. It can be left attached to the
           database handle and will continue monitoring for changes on the
           configured tables as before. However, if 
           [sqlite3session_changeset()] or [sqlite3session_patchset()] is
           called a second time on a session object, the changeset or patchset
           will contain <em>all</em> changes that have taken place on the connection
           since the session was created. In other words,
           a session object is not reset or
           zeroed by a call to sqlite3session_changeset() or
           sqlite3session_patchset().
</ol>

<codeblock class=C>
  /*
  ** Argument zSql points to a buffer containing an SQL script to execute 
  ** against the database handle passed as the first argument. As well as
  ** executing the SQL script, this function collects a changeset recording