From 9154a2f618238f577baa94ba777a47b4d6e95bed Mon Sep 17 00:00:00 2001 From: Boris Kolpackov Date: Sun, 16 Sep 2012 12:07:41 +0200 Subject: Change terminology ("additional type" to "extended type") --- doc/manual.xhtml | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) (limited to 'doc/manual.xhtml') diff --git a/doc/manual.xhtml b/doc/manual.xhtml index 518cf79..0b6155c 100644 --- a/doc/manual.xhtml +++ b/doc/manual.xhtml @@ -12882,13 +12882,13 @@ class object mapping between two database types. For each database system ODB provides built-in support for a core set of database types, such as integers, strings, binary, etc. However, many database - systems provide additional types such as extensions (geospatial, - key-value stores, etc.), user-defined types, and collections (arrays, - table types, etc). In order to support such additional types, ODB - allows us to map them to one of the built-in types, normally + systems provide extended types such as geospatial types, + user-defined types, and collections (arrays, table types, + key-value stores, etc). In order to support such extended types, + ODB allows us to map them to one of the built-in types, normally a string or a binary. Given the text or binary representation of the data we can then extract it into our chosen C++ data type - and thus establish a mapping between an additional database type and + and thus establish a mapping between an extended database type and its C++ equivalent.

The map pragma has the following format:

@@ -13075,7 +13075,7 @@ class object in a similar way. The odb-tests package contains a set of tests in the <database>/custom directories that, for each database, shows how to provide custom mapping for some of - the additional types.

+ the extended types.

12.8 C++ Compiler Warnings

-- cgit v1.1