From bfc6d29f8ef4efc48334cf0c25af433d85c21ed6 Mon Sep 17 00:00:00 2001
From: Boris Kolpackov <boris@codesynthesis.com>
Date: Thu, 29 Nov 2012 11:32:44 +0200
Subject: 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.
---
 odb/sqlite/forward.hxx | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)

(limited to 'odb/sqlite/forward.hxx')

diff --git a/odb/sqlite/forward.hxx b/odb/sqlite/forward.hxx
index e2f4df1..382284e 100644
--- a/odb/sqlite/forward.hxx
+++ b/odb/sqlite/forward.hxx
@@ -13,6 +13,13 @@ namespace odb
 {
   namespace sqlite
   {
+    namespace core
+    {
+      using namespace odb::common;
+    }
+
+    //
+    //
     class database;
     class connection;
     typedef details::shared_ptr<connection> connection_ptr;
@@ -21,6 +28,15 @@ namespace odb
     class transaction;
     class tracer;
 
+    namespace core
+    {
+      using sqlite::database;
+      using sqlite::connection;
+      using sqlite::connection_ptr;
+      using sqlite::transaction;
+      using sqlite::statement;
+    }
+
     // Implementation details.
     //
     enum statement_kind
-- 
cgit v1.1