delta/python-packages/sqlalchemy.git/lib/sqlalchemy, branch pr/51

Remove terminated connections from the pool.

2013-12-16T20:50:10+00:00

In pymssql, if you terminate a long running query manually
it will give you a connection reset by peer message, but this
connection remains in the pool and will be re-used.

wrong method name

2013-12-16T19:35:51+00:00

- add "force_nocheck" as a way to turn on unicode=force without even

2013-12-16T02:23:01+00:00

doing the isinstance() check - currently used only by psycopg2 + native enum + py2k.
- didn't realize psycopg2 had UNICODEARRAY extension all this time; replace _PGArray
with just using UNICODEARRAY instead.
- replace unnecessary/inconsistent __import__ in _isolation_lookup.

load_on_pending is different from enable_relationship_loading and should

2013-12-16T01:06:27+00:00

not be superseded.  both have a potential use.

make the error message for [ticket:2889] more accurate, as we support

2013-12-12T18:36:58+00:00

composites to many-to-ones now also

- :func:`.composite` will raise an informative error message when the

2013-12-12T18:30:16+00:00

columns/attribute (names) passed don't resolve to a Column or mapped
attribute (such as an erroneous tuple); previously raised an unbound
local. [ticket:2889]

- Error message when a string arg sent to :func:`.relationship` which

2013-12-12T17:49:57+00:00

doesn't resolve to a class or mapper has been corrected to work
the same way as when a non-string arg is received, which indicates
the name of the relationship which had the configurational error.
[ticket:2888]

- implement "literal binds" for the text() clause, [ticket:2882]

2013-12-12T01:00:39+00:00

- The :class:`.ForeignKey` class more aggressively checks the given

2013-12-12T00:48:27+00:00

column argument.   If not a string, it checks that the object is
at least a :class:`.ColumnClause`, or an object that resolves to one,
and that the ``.table`` attribute, if present, refers to a
:class:`.TableClause` or subclass, and not something like an
:class:`.Alias`.  Otherwise, a :class:`.ArgumentError` is raised.
[ticket:2883]

- The :class:`.exc.StatementError` or DBAPI-related subclass

2013-12-11T19:30:18+00:00

now can accomodate additional information about the "reason" for
the exception; the :class:`.Session` now adds some detail to it
when the exception occurs within an autoflush.  This approach
is taken as opposed to combining :class:`.FlushError` with
a Python 3 style "chained exception" approach so as to maintain
compatibility both with Py2K code as well as code that already
catches ``IntegrityError`` or similar.