delta/python-packages/sqlalchemy.git/lib/sqlalchemy/schema.py, branch pr_github_383 github.com: zzzeek/sqlalchemy.git Implement comments for tables, columns 2017-03-17T18:02:15+00:00 Frazer McLean frazer@frazermclean.co.uk 2016-06-11T19:47:33+00:00 fadb8d61babb76ef7bdbc98279096a8900c7328d Added support for SQL comments on :class:`.Table` and :class:`.Column` objects, via the new :paramref:`.Table.comment` and :paramref:`.Column.comment` arguments. The comments are included as part of DDL on table creation, either inline or via an appropriate ALTER statement, and are also reflected back within table reflection, as well as via the :class:`.Inspector`. Supported backends currently include MySQL, Postgresql, and Oracle. Co-authored-by: Mike Bayer <mike_mp@zzzcomputing.com> Fixes: #1546 Change-Id: Ib90683850805a2b4ee198e420dc294f32f15d35d 
Added support for SQL comments on :class:`.Table` and :class:`.Column`
objects, via the new :paramref:`.Table.comment` and
:paramref:`.Column.comment` arguments.   The comments are included
as part of DDL on table creation, either inline or via an appropriate
ALTER statement, and are also reflected back within table reflection,
as well as via the :class:`.Inspector`.   Supported backends currently
include MySQL, Postgresql, and Oracle.

Co-authored-by: Mike Bayer <mike_mp@zzzcomputing.com>
Fixes: #1546
Change-Id: Ib90683850805a2b4ee198e420dc294f32f15d35d
update for 2017 copyright 2017-01-04T17:39:24+00:00 Mike Bayer mike_mp@zzzcomputing.com 2017-01-04T17:39:24+00:00 64e72b58fd74db0c5c87407c824d08ad699e5e8e Change-Id: I4e8c2aa8fe817bb2af8707410fa0201f938781de 
Change-Id: I4e8c2aa8fe817bb2af8707410fa0201f938781de
Support "blank" schema when MetaData.schema is set 2016-05-18T15:43:38+00:00 Mike Bayer mike_mp@zzzcomputing.com 2016-05-18T15:07:02+00:00 c124fa36d5af2c85c87c51d24e92387adffbe3d2 Previously, it was impossible to have a Table that has None for a schema name when the "schema" parameter on MetaData was set. A new symbol sqlalchemy.schema.BLANK_SCHEMA is added which indicates that the schema name should unconditionally be set to None. In particular, this value must be passed within cross-schema foreign key reflection, so that a Table which is in the "default" schema can be represented properly. Fixes: #3716 Change-Id: I3d24f99c22cded206c5379fd32a225e74edb7a8e 
Previously, it was impossible to have a Table that has
None for a schema name when the "schema" parameter on
MetaData was set.  A new symbol sqlalchemy.schema.BLANK_SCHEMA
is added which indicates that the schema name should unconditionally
be set to None.  In particular, this value must be passed within
cross-schema foreign key reflection, so that a Table which
is in the "default" schema can be represented properly.

Fixes: #3716
Change-Id: I3d24f99c22cded206c5379fd32a225e74edb7a8e
- happy new year 2016-01-29T16:20:22+00:00 Mike Bayer mike_mp@zzzcomputing.com 2016-01-29T16:20:22+00:00 859379e2fcc4506d036700ba1eca4c0ae526a8ee 






- copyright 2015
2015-03-10T19:24:28+00:00

Mike Bayer
mike_mp@zzzcomputing.com

2015-03-10T19:24:28+00:00

50866d2f857dd45bb2d186a0fa076768437d62a3












- restate sort_tables in terms of a more fine grained
2015-01-02T01:17:06+00:00

Mike Bayer
mike_mp@zzzcomputing.com

2015-01-01T18:47:08+00:00

21f47124ab433cc74fa0a72efcc8a6c1e9c37db5

sort_tables_and_constraints function.
- The DDL generation system of :meth:`.MetaData.create_all`
and :meth:`.Metadata.drop_all` has been enhanced to in most
cases automatically handle the case of mutually dependent
foreign key constraints; the need for the
:paramref:`.ForeignKeyConstraint.use_alter` flag is greatly
reduced.  The system also works for constraints which aren't given
a name up front; only in the case of DROP is a name required for
at least one of the constraints involved in the cycle.
fixes #3282





sort_tables_and_constraints function.
- The DDL generation system of :meth:`.MetaData.create_all`
and :meth:`.Metadata.drop_all` has been enhanced to in most
cases automatically handle the case of mutually dependent
foreign key constraints; the need for the
:paramref:`.ForeignKeyConstraint.use_alter` flag is greatly
reduced.  The system also works for constraints which aren't given
a name up front; only in the case of DROP is a name required for
at least one of the constraints involved in the cycle.
fixes #3282







corrections
2014-12-27T21:54:32+00:00

Mike Bayer
mike_mp@zzzcomputing.com

2014-12-27T21:54:32+00:00

5343d24fee5219de002a8efba8bc882f8b3d4b5b












- break up the <authors> copyright comment as part of a pass
2014-07-09T22:26:55+00:00

Mike Bayer
mike_mp@zzzcomputing.com

2014-07-09T22:26:55+00:00

5407ec9d389cfa1cdd4ed4b82ba311085132d9db

to get all flake8 passing





to get all flake8 passing







Fix many typos throughout the codebase
2014-04-26T20:13:13+00:00

Alex Gaynor
alex.gaynor@gmail.com

2014-04-26T20:13:13+00:00

1caa7fafbd3c9870e1bf2b2ac623872447fc804e

Found using: https://github.com/intgr/topy





Found using: https://github.com/intgr/topy







- Added a new feature :func:`.schema.conv`, the purpose of which is to
2014-03-12T21:33:03+00:00

Mike Bayer
mike_mp@zzzcomputing.com

2014-03-12T21:33:03+00:00

36792434c74dea43a0f10f5fe1cc45c4206f01ee

mark a constraint name as already having had a naming convention applied.
This token will be used by Alembic migrations as of Alembic 0.6.4
in order to render constraints in migration scripts with names marked
as already having been subject to a naming convention.
re: #2991





mark a constraint name as already having had a naming convention applied.
This token will be used by Alembic migrations as of Alembic 0.6.4
in order to render constraints in migration scripts with names marked
as already having been subject to a naming convention.
re: #2991