Documentation Source Text
Check-in [ac94eb8835a06653934b3667fc70a66d627c8438]
Not logged in

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

Overview
SHA1 Hash:ac94eb8835a06653934b3667fc70a66d627c8438
Date: 2012-08-29 18:17:00
User: drh
Comment:Fix a few minor typos.
Tags And Properties
Changes
Hide Diffs Unified Diffs Ignore Whitespace Patch

Changes to pages/news.in

30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
  to simply remove the OS/2 code from the SQLite tree.  If there are
  OS/2 projects out there that still need SQLite support, they can
  continue to maintain their own private [VFS] which can be linked to
  SQLite at start-time using the [sqlite3_vfs_register()] interface.

  The [sqlite3_close_v2()] interface has been added.  The sqlite3_close_v2()
  interface differs from sqlite3_close() in that it is designed to work
  bettter for host language that use a garbage collector.  With the older
  sqlite3_close() interface, the associated [prepared statements] and
  [sqlite3_backup] objects must be destroyed before the database connection.
  With the newer sqlite3_close_v2() interface, the objects can be destroyed
  in any order.

  This release also includes proformance improvements to the sort algorithm
  that is used to implement ORDER BY and CREATE INDEX.
  
}

newsitem {2012-June-11} {Release 3.7.13} {
  SQLite [version 3.7.13] adds support for WinRT and metro style
  applications for Microsoft Windows 8.  The 3.7.13 release is







|





|







30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
  to simply remove the OS/2 code from the SQLite tree.  If there are
  OS/2 projects out there that still need SQLite support, they can
  continue to maintain their own private [VFS] which can be linked to
  SQLite at start-time using the [sqlite3_vfs_register()] interface.

  The [sqlite3_close_v2()] interface has been added.  The sqlite3_close_v2()
  interface differs from sqlite3_close() in that it is designed to work
  better for host language that use a garbage collector.  With the older
  sqlite3_close() interface, the associated [prepared statements] and
  [sqlite3_backup] objects must be destroyed before the database connection.
  With the newer sqlite3_close_v2() interface, the objects can be destroyed
  in any order.

  This release also includes preformance improvements to the sort algorithm
  that is used to implement ORDER BY and CREATE INDEX.
  
}

newsitem {2012-June-11} {Release 3.7.13} {
  SQLite [version 3.7.13] adds support for WinRT and metro style
  applications for Microsoft Windows 8.  The 3.7.13 release is

Changes to pages/sharedcache.in

244
245
246
247
248
249
250
251
252
253
254
255
256
databases if the unadorned name ":memory:" is used to open the database.
Prior to version 3.7.13, shared cache was always
disabled for in-memory databases regardless of the database name used,
current system shared cache setting, or query parameters or flags.
</p>

<p>
Enabling shared-cache for an in-mmeory database allows two or more
database connections in the same process to have access to the same
in-memory database.  An in-memory database in shared cache is automatically
deleted and memory is reclaimed when the last connection to that database
closes.
</p>







|





244
245
246
247
248
249
250
251
252
253
254
255
256
databases if the unadorned name ":memory:" is used to open the database.
Prior to version 3.7.13, shared cache was always
disabled for in-memory databases regardless of the database name used,
current system shared cache setting, or query parameters or flags.
</p>

<p>
Enabling shared-cache for an in-memory database allows two or more
database connections in the same process to have access to the same
in-memory database.  An in-memory database in shared cache is automatically
deleted and memory is reclaimed when the last connection to that database
closes.
</p>