delta/python-packages/sqlalchemy.git/test/engine, branch setinputsizes_oracle_string github.com: zzzeek/sqlalchemy.git Don't erase reflected comment in _init_existing 2017-06-20T13:48:49+00:00 Eloy Felix eloyfelix@gmail.com 2017-06-20T13:29:34+00:00 bff001187f5ad7192103d6255158a6c88e848049 Change-Id: Ie0b78c79367933486528ca0ba686d4a9f16922b1 Pull-request: https://github.com/zzzeek/sqlalchemy/pull/370 
Change-Id: Ie0b78c79367933486528ca0ba686d4a9f16922b1
Pull-request: https://github.com/zzzeek/sqlalchemy/pull/370
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
- keep trying to identify the race here. can reproduce locally 2017-04-27T21:44:29+00:00 Mike Bayer mike_mp@zzzcomputing.com 2017-04-27T21:44:29+00:00 cedb11925fc7dd652f479370b59c38324e0e3951 now and it seems like mock might not be doing the right thing. Change-Id: I5c108d82631c9217da54a8ace68d7728c3e204d8 
now and it seems like mock might not be doing the right thing.

Change-Id: I5c108d82631c9217da54a8ace68d7728c3e204d8
- try to work around a race that can occur in STP when 2017-04-27T19:26:35+00:00 Mike Bayer mike_mp@zzzcomputing.com 2017-04-27T19:26:35+00:00 1b63306a973f13588216fbb097b6dffb4a5c4c63 used in this intentionally broken scenario Change-Id: I88ea6fa710da2189e6d47e2d12f5f0fd6f6bb7d4 
used in this intentionally broken scenario

Change-Id: I88ea6fa710da2189e6d47e2d12f5f0fd6f6bb7d4
Apply type processing to untyped preexec default clause 2017-03-30T18:58:50+00:00 Mike Bayer mike_mp@zzzcomputing.com 2017-02-27T21:43:59+00:00 4eb4010c1a1c3e5c2529b9be9d8d56f1d6a4ec00 Fixed bug where a SQL-oriented Python-side column default could fail to be executed properly upon INSERT in the "pre-execute" codepath, if the SQL itself were an untyped expression, such as plain text. The "pre- execute" codepath is fairly uncommon however can apply to non-integer primary key columns with SQL defaults when RETURNING is not used. Tests exist here to ensure typing is applied to a typed expression for default, but in the case of an untyped SQL value, we know the type from the column, so apply this. Change-Id: I5d8b391611c137b9f700115a50a2bf5b30abfe94 Fixes: #3923 
Fixed bug where a SQL-oriented Python-side column default could fail to
be executed properly upon INSERT in the "pre-execute" codepath, if the
SQL itself were an untyped expression, such as plain text.  The "pre-
execute" codepath is fairly uncommon however can apply to non-integer
primary key columns with SQL defaults when RETURNING is not used.

Tests exist here to ensure typing is applied to
a typed expression for default, but in the case of
an untyped SQL value, we know the type from the column,
so apply this.

Change-Id: I5d8b391611c137b9f700115a50a2bf5b30abfe94
Fixes: #3923
Add safe_reraise() + warnings only to Connection._autorollback 2017-03-27T15:14:24+00:00 Mike Bayer mike_mp@zzzcomputing.com 2017-03-27T14:52:58+00:00 c0a224aba3d4e2a41f92a29f9d18c6cb9d09d61f Added an exception handler that will warn for the "cause" exception on Py2K when the "autorollback" feature of :class:`.Connection` itself raises an exception. In Py3K, the two exceptions are naturally reported by the interpreter as one occurring during the handling of the other. This is continuing with the series of changes for rollback failure handling that were last visited as part of :ticket:`2696` in 1.0.12. Change-Id: I600ba455a14ebaea27c6189889181f97c632f179 Fixes: #3946 
Added an exception handler that will warn for the "cause" exception on
Py2K when the "autorollback" feature of :class:`.Connection` itself
raises an exception. In Py3K, the two exceptions are naturally reported
by the interpreter as one occurring during the handling of the other.
This is continuing with the series of changes for rollback failure
handling that were last visited as part of :ticket:`2696` in 1.0.12.

Change-Id: I600ba455a14ebaea27c6189889181f97c632f179
Fixes: #3946
Integrate "pre-ping" into connection pool. 2017-03-20T22:01:23+00:00 Mike Bayer mike_mp@zzzcomputing.com 2017-02-24T15:50:14+00:00 f881dae8179b94f72ab0dc85d8f62be8c9ce2fe0 Added native "pessimistic disconnection" handling to the :class:`.Pool` object. The new parameter :paramref:`.Pool.pre_ping`, available from the engine as :paramref:`.create_engine.pool_pre_ping`, applies an efficient form of the "pre-ping" recipe featured in the pooling documentation, which upon each connection check out, emits a simple statement, typically "SELECT 1", to test the connection for liveness. If the existing connection is no longer able to respond to commands, the connection is transparently recycled, and all other connections made prior to the current timestamp are invalidated. Change-Id: I89700d0075e60abd2250e54b9bd14daf03c71c00 Fixes: #3919 
Added native "pessimistic disconnection" handling to the :class:`.Pool`
object.  The new parameter :paramref:`.Pool.pre_ping`, available from
the engine as :paramref:`.create_engine.pool_pre_ping`, applies an
efficient form of the "pre-ping" recipe featured in the pooling
documentation, which upon each connection check out, emits a simple
statement, typically "SELECT 1", to test the connection for liveness.
If the existing connection is no longer able to respond to commands,
the connection is transparently recycled, and all other connections
made prior to the current timestamp are invalidated.

Change-Id: I89700d0075e60abd2250e54b9bd14daf03c71c00
Fixes: #3919
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
Consult compiled paramstyle on execute_compiled 2017-03-15T14:40:30+00:00 Mike Bayer mike_mp@zzzcomputing.com 2017-03-15T14:15:12+00:00 7b056709c0f8a37744d18f37d40f94fa30c50c71 Fixed bug where in the unusual case of passing a :class:`.Compiled` object directly to :meth:`.Connection.execute`, the dialect with which the :class:`.Compiled` object were generated was not consulted for the paramstyle of the string statement, instead assuming it would match the dialect-level paramstyle, causing mismatches to occur. Change-Id: I114e4db2183fbb75bb7c0b0641f5a161855696ee Fixes: #3938 
Fixed bug where in the unusual case of passing a
:class:`.Compiled` object directly to :meth:`.Connection.execute`,
the dialect with which the :class:`.Compiled` object were generated
was not consulted for the paramstyle of the string statement, instead
assuming it would match the dialect-level paramstyle, causing
mismatches to occur.

Change-Id: I114e4db2183fbb75bb7c0b0641f5a161855696ee
Fixes: #3938
- add ad_hoc_engines to remove RealReconnectTest from oracle 2017-03-14T13:14:37+00:00 Mike Bayer mike_mp@zzzcomputing.com 2017-03-14T13:14:37+00:00 7b07ea67dc4a578be977a9f618dfb12fd12e852e Change-Id: Ie40aeba87dcfe9e8216abb8be050e7c2cc5b5ec9 
Change-Id: Ie40aeba87dcfe9e8216abb8be050e7c2cc5b5ec9