diff --git a/docs/patterns/sqlite3.rst b/docs/patterns/sqlite3.rst
index 1f9e3671..66a7c4c4 100644
--- a/docs/patterns/sqlite3.rst
+++ b/docs/patterns/sqlite3.rst
@@ -71,7 +71,8 @@ Now in each request handling function you can access `g.db` to get the
 current open database connection.  To simplify working with SQLite, a
 row factory function is useful.  It is executed for every result returned
 from the database to convert the result.  For instance, in order to get
-dictionaries instead of tuples, this could be inserted into ``get_db``::
+dictionaries instead of tuples, this could be inserted into the ``get_db`` 
+function we created above::
 
     def make_dicts(cursor, row):
         return dict((cursor.description[idx][0], value)
@@ -79,10 +80,26 @@ dictionaries instead of tuples, this could be inserted into ``get_db``::
 
     db.row_factory = make_dicts
 
-Or even simpler::
+This will make the sqlite3 module return dicts for this database connection, which are much nicer to deal with. Even more simply, we could place this in ``get_db`` instead::
 
     db.row_factory = sqlite3.Row
 
+This would use Row objects rather than dicts to return the results of queries. These are ``namedtuple`` s, so we can access them either by index or by key. For example, assuming we have a ``sqlite3.Row`` called ``r`` for the rows ``id``, ``FirstName``, ``LastName``, and ``MiddleInitial``::
+
+    >>> # You can get values based on the row's name
+    >>> r['FirstName']
+    John
+    >>> # Or, you can get them based on index
+    >>> r[1]
+    John
+    # Row objects are also iterable:
+    >>> for value in r:
+    ...     print(value)
+    1
+    John
+    Doe
+    M
+
 Additionally, it is a good idea to provide a query function that combines
 getting the cursor, executing and fetching the results::