From 1ac1ae65e6cbf42c002acb27615127bbc0b20d9e Mon Sep 17 00:00:00 2001 From: Boris Kolpackov Date: Mon, 4 Jul 2011 17:51:18 +0200 Subject: Fix terminology --- doc/manual.xhtml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/manual.xhtml b/doc/manual.xhtml index 385bb9d..b60eafc 100644 --- a/doc/manual.xhtml +++ b/doc/manual.xhtml @@ -5524,11 +5524,11 @@ t.commit (); a pre-allocated instance, the object is only cached if its object pointer is a raw pointer.

-

Finally, the session caches both constant and non-constant objects, +

Finally, the session caches both constant and unrestricted objects, depending on whether a constant reference or constant pointer was passed to the database::persist() function (in contrast, - when loaded, objects are always created and cached as non-constant). - If we try to load an object as non-constant that was previously + when loaded, objects are always created and cached as unrestricted). + If we try to load an object as unrestricted that was previously persisted and cached as constant, the odb::const_object exception is thrown. The following transaction shows the situation where this would happen:

-- cgit v1.1