diff options
| author | Boris Kolpackov <boris@codesynthesis.com> | 2012-11-29 11:32:43 +0200 |
|---|---|---|
| committer | Boris Kolpackov <boris@codesynthesis.com> | 2012-11-29 11:32:43 +0200 |
| commit | d5a8a14abbbdb41c753502ea25e2c327ada106f3 (patch) | |
| tree | 056cc6170f61cf4a4b535f5cc975d872db8601f2 /odb/nullable.hxx | |
| parent | d5e7059d8741c3a402d76b14209531474421ffac (diff) | |
Namespace management for static multi-database support
Now in libodb the odb::core namespace is split into odb::common (database-
independent stuff) and odb::core proper, which imports odb::common. Each
database runtime now defines odb::<db>::core namespace which also imports
odb::common and adds the database-specific bits. The overall idea is that
one can do using namespace odb::<db>::core just like for odb::core.
Diffstat (limited to 'odb/nullable.hxx')
| -rw-r--r-- | odb/nullable.hxx | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/odb/nullable.hxx b/odb/nullable.hxx index e3c9bc8..565b4ee 100644 --- a/odb/nullable.hxx +++ b/odb/nullable.hxx @@ -7,6 +7,8 @@ #include <odb/pre.hxx> +#include <odb/forward.hxx> // odb::core + namespace odb { template <typename T> @@ -52,7 +54,7 @@ namespace odb bool null_; }; - namespace core + namespace common { using odb::nullable; } |