added "system=True" to Column, so that we generally don't have to bother

with CreateColumn rules

Author: zzzeek

doc/build/changelog/changelog_08.rst

@@ -9,7 +9,12 @@
     .. change::
         :tags: feature
 
-        The :class:`.CreateColumn` construct can be appled to a custom
+        Added a new flag ``system=True`` to :class:`.Column`, which marks
+        the column as a "system" column which is automatically made present
+        by the database (such as Postgresql ``oid`` or ``xmin``).  The
+        column will be omitted from the ``CREATE TABLE`` statement but will
+        otherwise be available for querying.   In addition, the
+        :class:`.CreateColumn` construct can be appled to a custom
         compilation rule which allows skipping of columns, by producing
         a rule that returns ``None``.
 

doc/build/changelog/changelog_09.rst

@@ -9,7 +9,12 @@
     .. change::
         :tags: feature
 
-        The :class:`.CreateColumn` construct can be appled to a custom
+        Added a new flag ``system=True`` to :class:`.Column`, which marks
+        the column as a "system" column which is automatically made present
+        by the database (such as Postgresql ``oid`` or ``xmin``).  The
+        column will be omitted from the ``CREATE TABLE`` statement but will
+        otherwise be available for querying.   In addition, the
+        :class:`.CreateColumn` construct can be appled to a custom
         compilation rule which allows skipping of columns, by producing
         a rule that returns ``None``.  Also in 0.8.3.
 

lib/sqlalchemy/sql/compiler.py

@@ -2205,6 +2205,9 @@ def visit_create_table(self, create):
     def visit_create_column(self, create, first_pk=False):
         column = create.element
 
+        if column.system:
+            return None
+
         text = self.get_column_specification(
                         column,
                         first_pk=first_pk

lib/sqlalchemy/sql/ddl.py

@@ -551,13 +551,18 @@ def compile(element, compiler, **kw):
     The :class:`.CreateColumn` construct can also be used to skip certain
     columns when producing a ``CREATE TABLE``.  This is accomplished by
     creating a compilation rule that conditionally returns ``None``.
-    For example, to produce a
-    :class:`.Table` which includes the Postgresql system column ``xmin``,
-    but omits this column from the ``CREATE TABLE``::
+    This is essentially how to produce the same effect as using the
+    ``system=True`` argument on :class:`.Column`, which marks a column
+    as an implicitly-present "system" column.
+
+    For example, suppose we wish to produce a :class:`.Table` which skips
+    rendering of the Postgresql ``xmin`` column against the Postgresql backend,
+    but on other backends does render it, in anticipation of a triggered rule.
+    A conditional compilation rule could skip this name only on Postgresql::
 
         from sqlalchemy.schema import CreateColumn
 
-        @compiles(CreateColumn)
+        @compiles(CreateColumn, "postgresql")
         def skip_xmin(element, compiler, **kw):
             if element.element.name == 'xmin':
                 return None
@@ -572,7 +577,7 @@ def skip_xmin(element, compiler, **kw):
 
     Above, a :class:`.CreateTable` construct will generate a ``CREATE TABLE``
     which only includes the ``id`` column in the string; the ``xmin`` column
-    will be omitted.
+    will be omitted, but only against the Postgresql backend.
 
     .. versionadded:: 0.8.3 The :class:`.CreateColumn` construct supports
        skipping of columns by returning ``None`` from a custom compilation rule.

lib/sqlalchemy/sql/schema.py

@@ -893,6 +893,18 @@ def __init__(self, *args, **kwargs):
              an explicit name, use the :class:`.UniqueConstraint` or
              :class:`.Index` constructs explicitly.
 
+        :param system: When ``True``, indicates this is a "system" column,
+             that is a column which is automatically made available by the
+             database, and should not be included in the columns list for a
+             ``CREATE TABLE`` statement.
+
+             For more elaborate scenarios where columns should be conditionally
+             rendered differently on different backends, consider custom
+             compilation rules for :class:`.CreateColumn`.
+
+             ..versionadded:: 0.8.3 Added the ``system=True`` parameter to
+               :class:`.Column`.
+
         """
 
         name = kwargs.pop('name', None)
@@ -922,6 +934,7 @@ def __init__(self, *args, **kwargs):
         self.server_onupdate = kwargs.pop('server_onupdate', None)
         self.index = kwargs.pop('index', None)
         self.unique = kwargs.pop('unique', None)
+        self.system = kwargs.pop('system', False)
         self.quote = kwargs.pop('quote', None)
         self.doc = kwargs.pop('doc', None)
         self.onupdate = kwargs.pop('onupdate', None)

test/sql/test_compiler.py

@@ -2800,6 +2800,15 @@ def test_reraise_of_column_spec_issue_unicode(self):
             schema.CreateTable(t1).compile
         )
 
+    def test_system_flag(self):
+        m = MetaData()
+        t = Table('t', m, Column('x', Integer),
+                            Column('y', Integer, system=True),
+                            Column('z', Integer))
+        self.assert_compile(
+            schema.CreateTable(t),
+            "CREATE TABLE t (x INTEGER, z INTEGER)"
+        )
 
 class InlineDefaultTest(fixtures.TestBase, AssertsCompiledSQL):
     __dialect__ = 'default'