- a few tweaks to allow "server_defaults" to be a little more linkable;

remove "undoc members" that was putting some random server_default
atributes from ColumnClause

(cherry picked from commit 270301890ae87ec32a46bb17889d9776b7de1468)

1 files changed, 10 insertions, 2 deletions

diff --git a/lib/sqlalchemy/sql/schema.py b/lib/sqlalchemy/sql/schema.py
index 25eb68f6f..42dbe72b2 100644
--- a/lib/sqlalchemy/sql/schema.py
+++ b/lib/sqlalchemy/sql/schema.py
@@ -990,8 +990,12 @@ class Column(SchemaItem, ColumnClause):
             a positional argument; see that class for full detail on the
             structure of the argument.
 
-            Contrast this argument to ``server_default`` which creates a
-            default generator on the database side.
+            Contrast this argument to :paramref:`.Column.server_default`
+            which creates a default generator on the database side.
+
+            .. seealso::
+
+                :ref:`metadata_defaults_toplevel`
 
         :param doc: optional String that can be used by the ORM or similar
             to document attributes.   This attribute does not render SQL
@@ -1057,6 +1061,10 @@ class Column(SchemaItem, ColumnClause):
             construct does not specify any DDL and the implementation is left
             to the database, such as via a trigger.
 
+            .. seealso::
+
+                :ref:`server_defaults`
+
         :param server_onupdate:   A :class:`.FetchedValue` instance
              representing a database-side default generation function. This
              indicates to SQLAlchemy that a newly generated value will be