aboutsummaryrefslogtreecommitdiff
path: root/odb/mssql/forward.hxx
diff options
context:
space:
mode:
authorBoris Kolpackov <boris@codesynthesis.com>2012-11-29 11:32:43 +0200
committerBoris Kolpackov <boris@codesynthesis.com>2012-11-29 11:32:43 +0200
commit9f0b648c14bbb6dbb1a36c9bd4d88c5773c72ca0 (patch)
tree1f831fefcf6a5bc6e4a5bfb4113977b61f01bb7f /odb/mssql/forward.hxx
parente04895dcc4008a8c0cf53f34ef787a9c686ebcde (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/mssql/forward.hxx')
-rw-r--r--odb/mssql/forward.hxx16
1 files changed, 16 insertions, 0 deletions
diff --git a/odb/mssql/forward.hxx b/odb/mssql/forward.hxx
index 2a91c62..2bb21e3 100644
--- a/odb/mssql/forward.hxx
+++ b/odb/mssql/forward.hxx
@@ -13,6 +13,13 @@ namespace odb
{
namespace mssql
{
+ 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 mssql::database;
+ using mssql::connection;
+ using mssql::connection_ptr;
+ using mssql::transaction;
+ using mssql::statement;
+ }
+
// Implementation details.
//
enum statement_kind