delta/python-packages/sqlalchemy.git, branch rel_2_0_exp1

initial 2.0 setup

2019-12-01T16:15:44+00:00

For the moment, I think removing ./lib/ is just not going to be
possible because we still need lots of cross-merges between
1.4 and 2.0.   Unfortunately I think we are stuck with it.

As for other 2.0 related things, we are still watching 1.4
move along and I don't think we are ready for the "official"
2.0 branch yet, as it will keep getting too far behind.
So for now, maintain one or more "experimental" 2.0 branches
where we can at least maintain commits we are going to need,
like adding the 2.0 migration and all that stuff.   But
don't name anything "rel_2_0" yet and these branches can
disappear at any time.

Change-Id: Ib5af75df94b23104eebe0e918adcf979d798ea3b

Merge "Add DATETIMEOFFSET support for mssql+pyodbc"

2019-11-30T18:31:59+00:00

Add DATETIMEOFFSET support for mssql+pyodbc

2019-11-29T17:06:48+00:00

Repaired support for the :class:`.mssql.DATETIMEOFFSET` datatype on PyODBC,
by adding PyODBC-level result handlers as it does not include native
support for this datatype.  This includes usage of the Python 3 "timezone"
tzinfo subclass in order to set up a timezone, which on Python 2 makes
use of a minimal backport of "timezone" in sqlalchemy.util.

Fixes: #4983
Closes: #4986
Pull-request: https://github.com/sqlalchemy/sqlalchemy/pull/4986
Pull-request-sha: e3a5a8dda01c7580dc93271092c4f9beaac4be11

Change-Id: Ia4c7c0d1971c6c0492515bd5fa0b1799f07fee1c

Gracefully degrade for SQLite JSON receiving direct numeric value

2019-11-29T15:54:12+00:00

Fixed issue to workaround SQLite's behavior of assigning "numeric" affinity
to JSON datatypes, first described at :ref:`change_3850`, which returns
scalar numeric JSON values as a number and not as a string that can be JSON
deserialized.  The SQLite-specific JSON deserializer now gracefully
degrades for this case as an exception and bypasses deserialization for
single numeric values, as from a JSON perspective they are already
deserialized.

Also adds a combinatoric fixture for JSON single values within
the dialect-general test suite.

Fixes: #5014
Change-Id: Id38221dce1271fec527ca198b23908547b25d8a0

Merge "Remove ORM elements from annotations at the schema level."

2019-11-26T18:06:45+00:00

Merge "Add sequence support for MariaDB 10.3+."

2019-11-26T17:59:53+00:00

Don't clear metadata in TablesTest setup

2019-11-26T16:09:00+00:00

Some upcoming commits will make use of @metadata_fixture
within a TablesTest class.  As the fixture takes place before
setup, remove anything in setup that would interfere with it.

Change-Id: I4f16889c4c02cb2835dcf4886eb09ece848d8109
References: I507bc405eee6cae2c5991345d0eac53a37fe7512

Add sequence support for MariaDB 10.3+.

2019-11-26T16:06:37+00:00

Added support for use of the :class:`.Sequence` construct with MariaDB 10.3
and greater, as this is now supported by this database.  The construct
integrates with the :class:`.Table` object in the same way that it does for
other databases like PostrgreSQL and Oracle; if is present on the integer
primary key "autoincrement" column, it is used to generate defaults.   For
backwards compatibility, to support a :class:`.Table` that has a
:class:`.Sequence` on it to support sequence only databases like Oracle,
while still not having the sequence fire off for MariaDB, the optional=True
flag should be set, which indicates the sequence should only be used to
generate the primary key if the target database offers no other option.

Fixes: #4976
Closes: #4996
Pull-request: https://github.com/sqlalchemy/sqlalchemy/pull/4996
Pull-request-sha: cb2e1426ea0b6bc6c93dbe8f033a11df9d8c4915

Change-Id: I507bc405eee6cae2c5991345d0eac53a37fe7512

Remove ORM elements from annotations at the schema level.

2019-11-26T15:42:17+00:00

Fixed issue where when constructing constraints from ORM-bound columns,
primarily :class:`.ForeignKey` objects but also :class:`.UniqueConstraint`,
:class:`.CheckConstraint` and others, the ORM-level
:class:`.InstrumentedAttribute` is discarded entirely, and all ORM-level
annotations from the columns are removed; this is so that the constraints
are still fully pickleable without the ORM-level entities being pulled in.
These annotations are not necessary to be present at the schema/metadata
level.

Fully implemented coercions for constraint columns within
schema.py, including for FK referenced columns.

Fixes: #5001
Change-Id: I895400dd979310be034085d207f096707c635909

Generalize DescriptorProps.uses_objects

2019-11-23T17:30:43+00:00

Previously, uses_objects was specific to the SynonymAttribute;
generalize it so that it defaults to False for other DescriptorProps.
Immediate fix is against CompositeProperty.

Fixed regression introduced in 1.3.0 related to the association proxy
refactor in :ticket:`4351` that prevented :func:`.composite` attributes
from working in terms of an association proxy that references them.

Add test coverage for association proxies that refer to Composite
attributes as endpoints.

Fixes: #5000
Change-Id: Iea6fb1bd3314d861a9bc22491b0ae1e6c5e6340d