delta/python-packages/sqlalchemy.git/lib/sqlalchemy/dialects, branch setinputsizes_oracle_string github.com: zzzeek/sqlalchemy.git See what happens if we setinputsizes for String 2017-07-28T22:04:02+00:00 Mike Bayer mike_mp@zzzcomputing.com 2017-07-28T21:50:21+00:00 f83cbd50d7d0710f9bd174690cd2ef17f91122f3 Per Anthony Tuininga, setinputsizes() is important particularly if you have a unicode value you want to line up with an index under Python 3, because you want the type to be bound using NVARCHAR2 and not VARCHAR2. Only if we setinputsizes() for NVARCHAR2 will we get that effect. So see at least if setinputsizes() works for STRING these days or otherwise figure out what the problem was. Additionally, the type object now for NVARCHAR2 is cx_Oracle.NCHAR, so use that, and also remove some old _cx_oracle_XYZ collections we aren't using to reduce verbosity. Change-Id: I4977f54796485ec454b20697ec20db6d70fb6f84 
Per Anthony Tuininga, setinputsizes() is important
particularly if you have a unicode value you want to line
up with an index under Python 3, because you want the type
to be bound using NVARCHAR2 and not VARCHAR2.   Only if
we setinputsizes() for NVARCHAR2 will we get that effect.
So see at least if setinputsizes() works for STRING these
days or otherwise figure out what the problem was.

Additionally, the type object now for NVARCHAR2 is
cx_Oracle.NCHAR, so use that, and also remove some
old _cx_oracle_XYZ collections we aren't using to
reduce verbosity.

Change-Id: I4977f54796485ec454b20697ec20db6d70fb6f84
Revert cx_Oracle WITH_UNICODE change under > 5.0 2017-07-28T21:36:08+00:00 Mike Bayer mike_mp@zzzcomputing.com 2017-07-28T19:05:25+00:00 7997d7fdc3634e7dba9fd0113b8b85ef311bfeaa Fixed performance regression caused by the fix for :ticket:`3937` where cx_Oracle as of version 5.3 dropped the ``.UNICODE`` symbol from its namespace, which was interpreted as cx_Oracle's "WITH_UNICODE" mode being turned on unconditionally, which invokes functions on the SQLAlchemy side which convert all strings to unicode unconditionally and causing a performance impact. In fact, per cx_Oracle's author the "WITH_UNICODE" mode has been removed entirely as of 5.1, so the expensive unicode conversion functions are no longer necessary and are disabled if cx_Oracle 5.1 or greater is detected under Python 2. The warning against "WITH_UNICODE" mode that was removed under :ticket:`3937` is also restored. Change-Id: Iddd38d81a5adb27c953a5ee2eae5529a21da16e1 Fixes: #4035 
Fixed performance regression caused by the fix for :ticket:`3937` where
cx_Oracle as of version 5.3 dropped the ``.UNICODE`` symbol from its
namespace,  which was interpreted as cx_Oracle's "WITH_UNICODE" mode being
turned on unconditionally, which invokes functions on the SQLAlchemy
side which convert all strings to unicode unconditionally and causing
a performance impact.  In fact, per cx_Oracle's author the
"WITH_UNICODE" mode has been removed entirely as of 5.1, so the expensive unicode
conversion functions are no longer necessary and are disabled if
cx_Oracle 5.1 or greater is detected under Python 2.  The warning against
"WITH_UNICODE" mode that was removed under :ticket:`3937` is also restored.

Change-Id: Iddd38d81a5adb27c953a5ee2eae5529a21da16e1
Fixes: #4035
Implement MySQL's ON DUPLICATE KEY UPDATE 2017-07-03T18:38:09+00:00 Michael Doronin warrior2031@gmail.com 2017-06-15T14:11:49+00:00 7d3da6f850dca54b941275279470c37bec64a48f Added support for MySQL's ON DUPLICATE KEY UPDATE MySQL-specific :class:`.mysql.dml.Insert` object. Pull request courtesy Michael Doronin. Co-authored-by: Mike Bayer <mike_mp@zzzcomputing.com> Resolves: #4009 Change-Id: Ic71424f3c88af6082b48a910a2efb7fbfc0a7eb4 Pull-request: https://github.com/zzzeek/sqlalchemy/pull/365 
Added support for MySQL's ON DUPLICATE KEY UPDATE
MySQL-specific :class:`.mysql.dml.Insert` object.
Pull request courtesy Michael Doronin.

Co-authored-by: Mike Bayer <mike_mp@zzzcomputing.com>
Resolves: #4009
Change-Id: Ic71424f3c88af6082b48a910a2efb7fbfc0a7eb4
Pull-request: https://github.com/zzzeek/sqlalchemy/pull/365
Handle SHOW VARIABLES returning no row 2017-06-16T19:52:46+00:00 Mike Bayer mike_mp@zzzcomputing.com 2017-06-16T17:30:25+00:00 5650a0c306391216a9c9ce1961c5b548e534b5eb MySQL 5.7 has introduced permission limiting for the "SHOW VARIABLES" command; the MySQL dialect will now handle when SHOW returns no row, in particular for the initial fetch of SQL_MODE, and will emit a warning that user permissions should be modified to allow the row to be present. Change-Id: I98e7a69230da397b17eae07b7e9d024fa7aeeb26 Fixes: #4007 
MySQL 5.7 has introduced permission limiting for the "SHOW VARIABLES"
command; the MySQL dialect will now handle when SHOW returns no
row, in particular for the initial fetch of SQL_MODE, and will
emit a warning that user permissions should be modified to allow the
row to be present.

Change-Id: I98e7a69230da397b17eae07b7e9d024fa7aeeb26
Fixes: #4007
Render ARRAY index embedded between type and COLLATE 2017-06-08T21:06:53+00:00 Mike Bayer mike_mp@zzzcomputing.com 2017-06-08T16:55:23+00:00 ec422fb70e0044ed42dcfda5fb1a7a65db322cf1 Fixed bug where using :class:`.ARRAY` with a string type that features a collation would fail to produce the correct syntax within CREATE TABLE. The "COLLATE" must appear to the right of the array dimensions, so we are using regexp substitution to insert the brackets in the appropriate place. A more heavyweight solution would be that datatypes know how to split up their base type vs. modifiers, but as this is so specific to Postgresql ARRAY it's better to handle these cases more locally. Change-Id: I394c3c673eb60689e51b5301e51651972cfdb4c0 Fixes: #4006 
Fixed bug where using :class:`.ARRAY` with a string type that
features a collation would fail to produce the correct syntax
within CREATE TABLE.

The "COLLATE" must appear to the right of the array dimensions,
so we are using regexp substitution to insert the brackets in the
appropriate place.  A more heavyweight solution would be that datatypes
know how to split up their base type vs. modifiers, but as this is
so specific to Postgresql ARRAY it's better to handle these cases
more locally.

Change-Id: I394c3c673eb60689e51b5301e51651972cfdb4c0
Fixes: #4006
Parse for Postgresql version w/ "beta" 2017-06-07T16:30:22+00:00 Mike Bayer mike_mp@zzzcomputing.com 2017-06-07T16:30:22+00:00 b6d3f60791834ead92564fc58afebc2c3eb4a2ff Continuing with the fix that correctly handles Postgresql version string "10devel" released in 1.1.8, an additional regexp bump to handle version strings of the form "10beta1". While Postgresql now offers better ways to get this information, we are sticking w/ the regexp at least through 1.1.x for the least amount of risk to compatibility w/ older or alternate Postgresql databases. Change-Id: I12ddb06465f7dcf80563c27632441ef5963f60d4 Fixes: #4005 
Continuing with the fix that correctly handles Postgresql
version string "10devel" released in 1.1.8, an additional regexp
bump to handle version strings of the form "10beta1".   While
Postgresql now offers better ways to get this information, we
are sticking w/ the regexp at least through 1.1.x for the least
amount of risk to compatibility w/ older or alternate Postgresql
databases.

Change-Id: I12ddb06465f7dcf80563c27632441ef5963f60d4
Fixes: #4005
Implement get_unique_constraints, get_check_constraints for Oracle 2017-05-30T21:14:22+00:00 Eloy Felix eloyfelix@gmail.com 2016-12-12T17:09:54+00:00 f8b4f7289e3b07be489ede3f54b983d1461a2ac4 Pull-request: https://github.com/zzzeek/sqlalchemy/pull/326 Pull-request: https://github.com/zzzeek/sqlalchemy/pull/342 Fixes: #4002 Change-Id: I221fe8ba305fc455a03e3a5d15f803bf8ee2e8fb 
Pull-request: https://github.com/zzzeek/sqlalchemy/pull/326
Pull-request: https://github.com/zzzeek/sqlalchemy/pull/342

Fixes: #4002
Change-Id: I221fe8ba305fc455a03e3a5d15f803bf8ee2e8fb
Add placeholder XML support 2017-05-26T15:24:25+00:00 Mike Bayer mike_mp@zzzcomputing.com 2017-05-26T15:24:25+00:00 b1369b47217558779a5b8a17ecd945cedd608dc7 Added a placeholder type :class:`.mssql.XML` to the SQL Server dialect, so that a reflected table which includes this type can be re-rendered as a CREATE TABLE. The type has no special round-trip behavior nor does it currently support additional qualifying arguments. Change-Id: I651fa729bd8e9b31a0b5effe0839aff077d77c46 Fixes: #3973 
Added a placeholder type :class:`.mssql.XML` to the SQL Server
dialect, so that a reflected table which includes this type can
be re-rendered as a CREATE TABLE.  The type has no special round-trip
behavior nor does it currently support additional qualifying
arguments.

Change-Id: I651fa729bd8e9b31a0b5effe0839aff077d77c46
Fixes: #3973
Remove twophase for cx_Oracle 6.x 2017-05-23T19:42:06+00:00 Mike Bayer mike_mp@zzzcomputing.com 2017-05-23T14:17:51+00:00 1b98ce355a60b7ad9898aeb412c21591bb438231 Support for two-phase transactions has been removed entirely for cx_Oracle when version 6.0b1 or later of the DBAPI is in use. The two- phase feature historically has never been usable under cx_Oracle 5.x in any case, and cx_Oracle 6.x has removed the connection-level "twophase" flag upon which this feature relied. Change-Id: I2e8161cc2bc12f4845c9224cd483038112fe9734 Fixes: #3997 
Support for two-phase transactions has been removed entirely for
cx_Oracle when version 6.0b1 or later of the DBAPI is in use.  The two-
phase feature historically has never been usable under cx_Oracle 5.x in
any case, and cx_Oracle 6.x has removed the connection-level "twophase"
flag upon which this feature relied.

Change-Id: I2e8161cc2bc12f4845c9224cd483038112fe9734
Fixes: #3997
Allow metadata.reflect() to recover from unreflectable tables 2017-05-22T19:51:07+00:00 Mike Bayer mike_mp@zzzcomputing.com 2017-05-22T18:08:55+00:00 9f0fb6c601829cb7c9f449d57e12e8b95dab51f5 Added support for views that are unreflectable due to stale table definitions, when calling :meth:`.MetaData.reflect`; a warning is emitted for the table that cannot respond to ``DESCRIBE`` but the operation succeeds. The MySQL dialect now raises UnreflectableTableError which is in turn caught by MetaData.reflect(). Reflecting the view standalone raises this error directly. Change-Id: Id8005219d8e073c154cc84a873df911b4a6cf4d6 Fixes: #3871 
Added support for views that are unreflectable due to stale
table definitions, when calling :meth:`.MetaData.reflect`; a warning
is emitted for the table that cannot respond to ``DESCRIBE``
but the operation succeeds.  The MySQL dialect now
raises UnreflectableTableError which is in turn caught by
MetaData.reflect().  Reflecting the view standalone raises
this error directly.

Change-Id: Id8005219d8e073c154cc84a873df911b4a6cf4d6
Fixes: #3871