From d5a8a14abbbdb41c753502ea25e2c327ada106f3 Mon Sep 17 00:00:00 2001
From: Boris Kolpackov <boris@codesynthesis.com>
Date: Thu, 29 Nov 2012 11:32:43 +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/result.hxx | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

(limited to 'odb/result.hxx')

diff --git a/odb/result.hxx b/odb/result.hxx
index 5db08cd..d90ceb0 100644
--- a/odb/result.hxx
+++ b/odb/result.hxx
@@ -9,7 +9,7 @@
 
 #include <cstddef>  // std::ptrdiff_t, std::size_t
 
-#include <odb/forward.hxx>
+#include <odb/forward.hxx> // odb::core
 #include <odb/traits.hxx>
 
 #include <odb/details/export.hxx>
@@ -215,7 +215,7 @@ namespace odb
     details::shared_ptr<result_impl_type> impl_;
   };
 
-  namespace core
+  namespace common
   {
     using odb::result;
     using odb::result_iterator;
-- 
cgit v1.1