delta/python-packages/sqlalchemy.git/lib/sqlalchemy/sql/schema.py, branch pr/41

Super-minor doc fix

2013-10-28T22:26:37+00:00

Merge branch 'master' of github.com:ijl/sqlalchemy into merge_2183

2013-10-25T21:01:38+00:00

- The :meth:`.Table.tometadata` method now produces copies of

2013-10-19T00:01:45+00:00

all :attr:`.SchemaItem.info` dictionaries from all :class:`.SchemaItem`
objects within the structure including columns, constraints,
foreign keys, etc.   As these dictionaries
are copies, they are independent of the original dictionary.
Previously, only the ``.info`` dictionary of :class:`.Column` was transferred
within this operation, and it was only linked in place, not copied.
[ticket:2716]

The ``.unique`` flag on :class:`.Index` could be produced as ``None``

2013-10-14T18:53:28+00:00

if it was generated from a :class:`.Column` that didn't specify ``unique``
(where it defaults to ``None``).  The flag will now always be ``True`` or
``False``. [ticket:2825]

#2183: Metadata.reflect() foreign keys include options when the dialect exposes it

2013-10-13T21:13:28+00:00

The ``default`` argument of :class:`.Column` now accepts a class

2013-10-11T20:16:08+00:00

or object method as an argument, in addition to a standalone function;
will properly detect if the "context" argument is accepted or not.

The "name" attribute is set on :class:`.Index` before the "attach"

2013-10-11T19:55:57+00:00

events are called, so that attachment events can be used to dynamically
generate a name for the index based on the parent table and/or
columns. [ticket:2835]

The erroneous kw arg "schema" has been removed from the :class:`.ForeignKey`

2013-10-08T23:20:09+00:00

object. this was an accidental commit that did nothing; a warning is raised
in 0.8.3 when this kw arg is used. [ticket:2831]

Replace a big loop + dict lookup in Connection.execute() with a simple visitor

2013-09-25T17:29:52+00:00

pattern

- A rework to the way that "quoted" identifiers are handled, in that

2013-08-28T00:43:22+00:00

instead of relying upon various ``quote=True`` flags being passed around,
these flags are converted into rich string objects with quoting information
included at the point at which they are passed to common schema constructs
like :class:`.Table`, :class:`.Column`, etc.   This solves the issue
of various methods that don't correctly honor the "quote" flag such
as :meth:`.Engine.has_table` and related methods.  The :class:`.quoted_name`
object is a string subclass that can also be used explicitly if needed;
the object will hold onto the quoting preferences passed and will
also bypass the "name normalization" performed by dialects that
standardize on uppercase symbols, such as Oracle, Firebird and DB2.
The upshot is that the "uppercase" backends can now work with force-quoted
names, such as lowercase-quoted names and new reserved words.
[ticket:2812]