- fix the marker here so this page can be found

- clarify the note about the defaults, note that it's upcoming in 1.0

diff --git a/doc/build/core/defaults.rst b/doc/build/core/defaults.rst
index 166273c186e84a96cd311308f4f47e5c7558c78a..7b426cf746e4c614b382a85d07744343585b234b 100644 (file)
--- a/doc/build/core/defaults.rst
+++ b/doc/build/core/defaults.rst
@@ -1,6 +1,7 @@
+.. module:: sqlalchemy.schema
+
 .. _metadata_defaults_toplevel:
 .. _metadata_defaults:
-.. module:: sqlalchemy.schema
 
 Column Insert/Update Defaults
 ==============================

diff --git a/lib/sqlalchemy/sql/dml.py b/lib/sqlalchemy/sql/dml.py
index 62be3a28653c3a4f358fbddcf3b9862bf8d11983..910806ebbee0df7bc77f1360a91283a40ec5ff5a 100644 (file)
--- a/lib/sqlalchemy/sql/dml.py
+++ b/lib/sqlalchemy/sql/dml.py
@@ -516,10 +516,12 @@ class Insert(ValuesBase):
 
         .. note::
 
-           A SELECT..INSERT construct in SQL has no VALUES clause.  Therefore
-           :class:`.Column` objects which utilize Python-side defaults
-           (e.g. as described at :ref:`metadata_defaults_toplevel`)
-           will **not** take effect when using :meth:`.Insert.from_select`.
+           Python-side and SQL function defaults, as described at
+           :ref:`metadata_defaults_toplevel`, are **not** automatically
+           included in the SELECT statement as rendered unless explicitly
+           added to the statement.  The behavior of automatically rendering
+           these default values and expressions is available as of SQLAlchemy
+           version 1.0.0.
 
         .. versionadded:: 0.8.3