From 888888eb63c367b47f2ad3e81408bfcc54e42e80 Mon Sep 17 00:00:00 2001
From: Boris Kolpackov
By default, all these mechanisms use raw pointers to return,
pass, and cache objects. This is normally sufficient for applications
that have simple object lifetime requirements and do not use sessions
- or object relationsips. In particular, a dynamically allocated object
- that is returned as a raw poiner from a database operation can be
+ or object relationships. In particular, a dynamically allocated object
+ that is returned as a raw pointer from a database operation can be
assigned to a smart pointer of our choice, for example
std::auto_ptr
or shared_ptr
from TR1 or
Boost.
The same can be acomplished using dynamically allocated objects +
The same can be accomplished using dynamically allocated objects
and the object pointer version of the update()
function,
for example:
While an ordinary member is mapped to one or more columns in the - object's table, a member of a container type is mapped to a seperate + object's table, a member of a container type is mapped to a separate table. The exact schema of such a table depends on the kind of a container. ODB defines the following container kinds: ordered, set, multiset, map, and multimap. The container kinds and the @@ -3389,7 +3389,7 @@ private:
In ODB map and multimap containers (referred to as just set
containers) are associative containers that contain key-value
- elemenst based on some relationship between keys. A map container
+ elements based on some relationship between keys. A map container
may or may not guarantee a particular order of the elements that
it stores. Standard C++ containers that are considered map
containers for the purpose of persistence include
@@ -4606,7 +4606,7 @@ class person
contains the name
scope (derived from the name_
data member) which in turn contains the extras
member
(derived from the name::extras_
data member of the
- composite value type). The process continues reqursively for nested
+ composite value type). The process continues recursively for nested
composite value types and, as a result, we can use the
query::name::extras::nickname
expression while querying
the database for the person
objects. For example:
odb::const_object
- exception is thrown. The following transaction illustartes the
+ exception is thrown. The following transaction illustrates the
situation where this would happen:
-- cgit v1.1