From d9e5b562c424cdf8b1fa3ca2a66c07f1a232d5be Mon Sep 17 00:00:00 2001
From: Trismegiste <florent.g@allopneus.com>
Date: Mon, 8 Jul 2013 04:23:56 +0200
Subject: [PATCH] injecting a database abstract layer (instead of creting it in
 constructor)

---
 DataMapper/UserMapper.php | 17 +++++++----------
 1 file changed, 7 insertions(+), 10 deletions(-)

diff --git a/DataMapper/UserMapper.php b/DataMapper/UserMapper.php
index 181d9fe..e6e6fa5 100644
--- a/DataMapper/UserMapper.php
+++ b/DataMapper/UserMapper.php
@@ -1,6 +1,6 @@
 <?php
 
-namespace DesignPatterns;
+namespace DesignPatterns\DataMapper;
 
 /**
  * DataMapper pattern
@@ -16,24 +16,21 @@ namespace DesignPatterns;
  * entity types, dedicated mappers will handle one or a few.
  * (FROM http://en.wikipedia.org/wiki/Data_mapper_pattern)
  *
+ * The key point of this pattern is, unlike Active Record pattern, the datamodel
+ * follows Single Responsibility Principle.
  *
  * Examples:
- * - DB Object Relational Mapper (ORM)
- *
+ * - DB Object Relational Mapper (ORM) : Doctrine2 uses DAO named as "EntityRepository"
+ * 
  */
 class UserMapper
 {
 
     protected $_adapter;
 
-    public function __construct(array $options = null)
+    public function __construct(DBAL $dbLayer)
     {
-        /**
-         * create new Database connector on $_adapter using specific table
-         *
-         * $_adapter var could be a specific to a table class or a generic 
-         * interface for connecting to Database and do certain jobs
-         */
+        $this->_adapter = $dbLayer;
     }
 
     /**