From 2deb85bd57bd1c31788e7236a17beff4fd3c3fa9 Mon Sep 17 00:00:00 2001
From: Boris Kolpackov <boris@codesynthesis.com>
Date: Wed, 2 Nov 2011 09:35:02 +0200
Subject: Optimize load_id(), load() sequence for SQLite and PostgreSQL

In these databases both of these functions load the data into the
object image. If there is no chance of image overwrite between
these calls, then we don't need to load the image the second time.
---
 odb/oracle/object-result.hxx | 2 +-
 odb/oracle/object-result.txx | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/odb/oracle/object-result.hxx b/odb/oracle/object-result.hxx
index 8751948..91683de 100644
--- a/odb/oracle/object-result.hxx
+++ b/odb/oracle/object-result.hxx
@@ -42,7 +42,7 @@ namespace odb
                           object_statements<object_type>&);
 
       virtual void
-      load (object_type&);
+      load (object_type&, bool fetch);
 
       virtual id_type
       load_id ();
diff --git a/odb/oracle/object-result.txx b/odb/oracle/object-result.txx
index c998e47..2b35c7b 100644
--- a/odb/oracle/object-result.txx
+++ b/odb/oracle/object-result.txx
@@ -46,7 +46,7 @@ namespace odb
 
     template <typename T>
     void object_result_impl<T>::
-    load (object_type& obj)
+    load (object_type& obj, bool)
     {
       // This is a top-level call so the statements cannot be locked.
       //
-- 
cgit v1.1