From 780b92ada9afcf1d58085a83a0b9e6bc982203d1 Mon Sep 17 00:00:00 2001 From: Lorry Tar Creator Date: Tue, 17 Feb 2015 17:25:57 +0000 Subject: Imported from /home/lorry/working-area/delta_berkeleydb/db-6.1.23.tar.gz. --- docs/programmer_reference/am_misc_perm.html | 43 ++++++++++++++++------------- 1 file changed, 24 insertions(+), 19 deletions(-) (limited to 'docs/programmer_reference/am_misc_perm.html') diff --git a/docs/programmer_reference/am_misc_perm.html b/docs/programmer_reference/am_misc_perm.html index de9c1164..f8631afc 100644 --- a/docs/programmer_reference/am_misc_perm.html +++ b/docs/programmer_reference/am_misc_perm.html @@ -14,7 +14,7 @@

Library Version 11.2.5.3

Library Version 12.1.6.1

@@ -22,9 +22,7 @@ - +

Prev	Chapter 4. - Access Method Wrapup -	Chapter 4. Access Method Wrapup	Next

@@ -38,20 +36,26 @@

When using the non-cursor Berkeley DB calls to retrieve key/data items under -the C/C++ APIs (for example, DB->get()), the memory to which the -pointer stored into the DBT refers is only valid until the next -call to Berkeley DB using the DB handle. (This includes any -use of the returned DB handle, including by another thread of -control within the process. For this reason, when multiple threads are -using the returned DB handle concurrently, one of the -DB_DBT_MALLOC, DB_DBT_REALLOC or DB_DBT_USERMEM -flags must be specified with any non-cursor DBT used for key or -data retrieval.)

When using the cursor Berkeley DB calls to retrieve key/data items under the -C/C++ APIs (for example, DBC->get()), the memory to which the -pointer stored into the DBT refers is only valid until the next -call to Berkeley DB using the DBC returned by DB->cursor().

+ When using the non-cursor Berkeley DB calls to retrieve + key/data items under the C/C++ APIs (for example, DB->get()), + the memory to which the pointer stored into the DBT refers + is only valid until the next call to Berkeley DB using the + DB handle. (This includes any use of the returned DB handle, including + by another thread of control within the process. For this + reason, when multiple threads are using the returned DB + handle concurrently, one of the DB_DBT_MALLOC, + DB_DBT_REALLOC or DB_DBT_USERMEM flags must be specified + with any non-cursor DBT used for key or data + retrieval.) +

+ When using the cursor Berkeley DB calls to retrieve key/data + items under the C/C++ APIs (for example, DBC->get()), the memory + to which the pointer stored into the DBT refers is only + valid until the next call to Berkeley DB using the DBC + returned by DB->cursor(). +

@@ -64,7 +68,8 @@ call to Berkeley DB using the Next - Storing C/C++ structures/objects + Storing C/C++ + structures/objects Home -- cgit v1.2.1