Suggested multiple entry documentation.

Advises that profile entries are not one to one for query statements, but rather one for each significant underlying method. This minimally addresses issue #99.
auraphp · Jun 4, 2015 · bd7f1a2 · bd7f1a2
1 parent 69ade8a
commit bd7f1a2
Showing 1 changed file with 2 additions and 0 deletions.
diff --git a/README.md b/README.md
@@ -328,6 +328,8 @@ Each profile entry will have these keys:
 - `trace`: An exception stack trace indicating where the query was issued from
   in the codebase.
 
+Note that an entry is made into the profile for each call to underlying _ExtendedPDO_ methods.  For example, in a simple query using a bind value, there will be two entries, one for the call to `prepare` and one for the call to `perform`.
+
 Setting the _Profiler_ into the _ExtendedPdo_ instance is optional. Once it
 is set, you can activate and deactivate it as you wish using the
 `Profiler::setActive()` method. When not active, query profiles will not be