* Support for the SQLite database, including shared cache and unlock
notification to aid concurrency. For more information, refer to
Chapter 11, "SQLite Database" in the ODB manual.
* New profile, boost, provides persistence support for the Boost libraries.
This version covers the most commonly used types from the smart_ptr,
unordered, and date_time libraries. The boost profile implementation is
provided by the libodb-boost library. For more information refer to
Chapter 11, "Profiles Introduction" and Chapter 12, "Boost Profile" in
the ODB manual as well as the 'boost' example in the odb-examples package.
* Support for embedded database schemas. The new option, --schema-format,
allows the selection of the schema format. The valid values for this
option are 'sql' for a standalone SQL file and 'embedded' for a schema
embedded into the generated C++ code. The new odb::schema_catalog class
provides support for accessing embedded schemas from within the
application. For details refer to Section 3.3, "Database" in the ODB
manual as well as the 'schema/embedded' example in the odb-examples
* New exceptions: odb::recoverable, odb::connection_lost, and odb::timeout.
The odb::recoverable exception is a common base class for all recoverable
ODB exceptions. The other two exceptions plus odb::deadlock now inherit
from this base. Refer to Section 3.5, "Error Handling and Recovery" for
* Support for connection validation (ping) in MySQL connection_pool_factory.
This transparently deals with the MySQL server closing connections after
a certain period of inactivity.
* New namespace, odb::core, contains using-declarations for the core ODB
constructs, such as the database, transaction, etc. The primary use of
this namespace is in the using-directives:
using namespace odb::core;
The above form should be preferred over the old variant:
using namespace odb;
The new approach brings all the essential ODB names into the current
namespace without any of the auxiliary objects such as traits, etc., which
minimizes the likelihood of conflicts with other libraries. Note that you
should still use the odb namespace when qualifying individual names, for
* New option aliases: -q for --generate-query and -s for --generate-schema.
* Support for the default options file. Now, if configured, the ODB compiler
loads the default options file (by default ../etc/odb/default.options,
relative to the ODB compiler binary). This file can be used for
installation-wide customization, such as adding extra include search
* Support for storing containers in the database. For more information refer
to Chapter 5, "Containers" in the ODB manual as well as the 'container'
example in the odb-examples package.
* Support for unidirectional and bidirectional object relationships,
including lazy loading. For more information refer to Chapter 6,
"Relationships" in the ODB manual as well as the 'relationship' and
'inverse' examples in the odb-examples package.
* Support for composite value types. For more information refer to Chapter
7, "Composite Value Types" in the ODB manual as well as the 'composite'
example in the odb-examples package.
* Support for sessions. A session is an application's unit of work that
may encompass several database transactions. In this version of ODB a
session is just an object cache. For more information refer to Chapter
8, "Session" in the ODB manual.
* Support for custom object pointers that allows you to use smart pointers
to return, pass, and cache persistent objects. See Section 3.2, "Object
Pointers" in the ODB manual for details.
* Support for native SQL statement execution. See Section 3.9, "Executing
Native SQL Statements" in the ODB manual for details.
* New option, --profile/-p, instructs the ODB compiler to use the specified
profile library. See the ODB compiler command line manual for details.
* Support for literal names (template-id, derived type declarator such as
pointers, etc) in data member declarations. Now, for example, you can use
std::vector<std::string> directly instead of having to create a typedef
alias for it.
* Support for inheritance from transient base types for object types and
composite value types.
* New example, 'schema/custom', shows how to map persistent C++ classes to
a custom database schema.
* New options, --odb-prologue, --odb-epilogue, allow inclusion of extra code
into the ODB compilation process. This can be useful for making additional
traits specializations or ODB pragmas known to the ODB compiler.
* Support for persistent classes without default constructors. For objects
of such classes only the load() and find() database functions that
populate an existing instance can be used. Similarly, only the load()
query result iterator function which populates an existing instance can
* Initial release.