- make inserted_primary_key a link and be more clear what happens here

(cherry picked from commit 86e5419968be23b88ef7e2ba4de9ca6698f0540b)

diff --git a/doc/build/core/tutorial.rst b/doc/build/core/tutorial.rst
index f7d2e8aa68c46ade6c7ba155f0fa6e04ff8dbc66..eb32743512d5e1247f22d2c36dcb20c1307eea5e 100644 (file)
--- a/doc/build/core/tutorial.rst
+++ b/doc/build/core/tutorial.rst
@@ -290,7 +290,8 @@ the SQLAlchemy :class:`~sqlalchemy.engine.Connection` object references a
 DBAPI connection, the result, known as a
 :class:`~sqlalchemy.engine.ResultProxy` object, is analogous to the DBAPI
 cursor object. In the case of an INSERT, we can get important information from
-it, such as the primary key values which were generated from our statement:
+it, such as the primary key values which were generated from our statement
+using :attr:`.ResultProxy.inserted_primary_key`:
 
 .. sourcecode:: pycon+sql
 
@@ -304,8 +305,11 @@ value would have been used. In either case, SQLAlchemy always knows how to get
 at a newly generated primary key value, even though the method of generating
 them is different across different databases; each database's
 :class:`~sqlalchemy.engine.interfaces.Dialect` knows the specific steps needed to
-determine the correct value (or values; note that ``inserted_primary_key``
-returns a list so that it supports composite primary keys).
+determine the correct value (or values; note that
+:attr:`.ResultProxy.inserted_primary_key`
+returns a list so that it supports composite primary keys).    Methods here
+range from using ``cursor.lastrowid``, to selecting from a database-specific
+function, to using ``INSERT..RETURNING`` syntax; this all occurs transparently.
 
 .. _execute_multiple: