delta/python-packages/sqlalchemy.git/test/dialect/test_sqlite.py, branch workflow_test_cython github.com: zzzeek/sqlalchemy.git Clean up most py3k compat 2021-11-25T03:51:27+00:00 Federico Caselli cfederico87@gmail.com 2021-11-21T20:17:27+00:00 31acba8ff7c123a20ae308b7f4ab6df3df264b48 Change-Id: I8172fdcc3103ff92aa049827728484c8779af6b7 
Change-Id: I8172fdcc3103ff92aa049827728484c8779af6b7
Remove object in class definition 2021-11-22T15:03:17+00:00 Federico Caselli cfederico87@gmail.com 2021-11-21T19:36:35+00:00 0b95f0055be252b13e99b0a944466f60b5e367ff References: #4600 Change-Id: I2a62ddfe00bc562720f0eae700a497495d7a987a 
References: #4600
Change-Id: I2a62ddfe00bc562720f0eae700a497495d7a987a
fully support isolation_level parameter in base dialect 2021-11-18T18:11:43+00:00 Mike Bayer mike_mp@zzzcomputing.com 2021-11-06T17:00:43+00:00 af1b91626f63e00e11d07ad378d23198abc7f91f Generalized the :paramref:`_sa.create_engine.isolation_level` parameter to the base dialect so that it is no longer dependent on individual dialects to be present. This parameter sets up the "isolation level" setting to occur for all new database connections as soon as they are created by the connection pool, where the value then stays set without being reset on every checkin. The :paramref:`_sa.create_engine.isolation_level` parameter is essentially equivalent in functionality to using the :paramref:`_engine.Engine.execution_options.isolation_level` parameter via :meth:`_engine.Engine.execution_options` for an engine-wide setting. The difference is in that the former setting assigns the isolation level just once when a connection is created, the latter sets and resets the given level on each connection checkout. Fixes: #6342 Change-Id: Id81d6b1c1a94371d901ada728a610696e09e9741 
Generalized the :paramref:`_sa.create_engine.isolation_level` parameter to
the base dialect so that it is no longer dependent on individual dialects
to be present. This parameter sets up the "isolation level" setting to
occur for all new database connections as soon as they are created by the
connection pool, where the value then stays set without being reset on
every checkin.

The :paramref:`_sa.create_engine.isolation_level` parameter is essentially
equivalent in functionality to using the
:paramref:`_engine.Engine.execution_options.isolation_level` parameter via
:meth:`_engine.Engine.execution_options` for an engine-wide setting. The
difference is in that the former setting assigns the isolation level just
once when a connection is created, the latter sets and resets the given
level on each connection checkout.

Fixes: #6342
Change-Id: Id81d6b1c1a94371d901ada728a610696e09e9741
change the POSTCOMPILE/ SCHEMA symbols to not conflict w mssql quoting 2021-11-09T20:30:58+00:00 Mike Bayer mike_mp@zzzcomputing.com 2021-11-08T23:29:16+00:00 b919a0a85afd5066f9188b20ef06ee1b4af884a9 Adjusted the compiler's generation of "post compile" symbols including those used for "expanding IN" as well as for the "schema translate map" to not be based directly on plain bracketed strings with underscores, as this conflicts directly with SQL Server's quoting format of also using brackets, which produces false matches when the compiler replaces "post compile" and "schema translate" symbols. The issue created easy to reproduce examples both with the :meth:`.Inspector.get_schema_names` method when used in conjunction with the :paramref:`_engine.Connection.execution_options.schema_translate_map` feature, as well in the unlikely case that a symbol overlapping with the internal name "POSTCOMPILE" would be used with a feature like "expanding in". Fixes: #7300 Change-Id: I6255c850b140522a4aba95085216d0bca18ce230 
Adjusted the compiler's generation of "post compile" symbols including
those used for "expanding IN" as well as for the "schema translate map" to
not be based directly on plain bracketed strings with underscores, as this
conflicts directly with SQL Server's quoting format of also using brackets,
which produces false matches when the compiler replaces "post compile" and
"schema translate" symbols. The issue created easy to reproduce examples
both with the :meth:`.Inspector.get_schema_names` method when used in
conjunction with the
:paramref:`_engine.Connection.execution_options.schema_translate_map`
feature, as well in the unlikely case that a symbol overlapping with the
internal name "POSTCOMPILE" would be used with a feature like "expanding
in".

Fixes: #7300
Change-Id: I6255c850b140522a4aba95085216d0bca18ce230
fully implement future engine and remove legacy 2021-11-07T19:30:35+00:00 Mike Bayer mike_mp@zzzcomputing.com 2021-11-01T19:44:44+00:00 d050193daaa8d91371c759296f3304b8641c1976 The major action here is to lift and move future.Connection and future.Engine fully into sqlalchemy.engine.base. This removes lots of engine concepts, including: * autocommit * Connection running without a transaction, autobegin is now present in all cases * most "autorollback" is obsolete * Core-level subtransactions (i.e. MarkerTransaction) * "branched" connections, copies of connections * execution_options() returns self, not a new connection * old argument formats, distill_params(), simplifies calling scheme between engine methods * before/after_execute() events (oriented towards compiled constructs) don't emit for exec_driver_sql(). before/after_cursor_execute() is still included for this * old helper methods superseded by context managers, connection.transaction(), engine.transaction() engine.run_callable() * ancient engine-level reflection methods has_table(), table_names() * sqlalchemy.testing.engines.proxying_engine References: #7257 Change-Id: Ib20ed816642d873b84221378a9ec34480e01e82c 
The major action here is to lift and move future.Connection
and future.Engine fully into sqlalchemy.engine.base.   This
removes lots of engine concepts, including:

* autocommit
* Connection running without a transaction, autobegin
  is now present in all cases
* most "autorollback" is obsolete
* Core-level subtransactions (i.e. MarkerTransaction)
* "branched" connections, copies of connections
* execution_options() returns self, not a new connection
* old argument formats, distill_params(), simplifies calling
  scheme between engine methods
* before/after_execute() events (oriented towards compiled constructs)
  don't emit for exec_driver_sql().  before/after_cursor_execute()
  is still included for this
* old helper methods superseded by context managers, connection.transaction(),
  engine.transaction() engine.run_callable()
* ancient engine-level reflection methods has_table(), table_names()
* sqlalchemy.testing.engines.proxying_engine

References: #7257

Change-Id: Ib20ed816642d873b84221378a9ec34480e01e82c
First round of removal of python 2 2021-11-01T19:11:25+00:00 Federico Caselli cfederico87@gmail.com 2021-10-30T20:00:25+00:00 36e7aebd8d6faac77570403e99f9aa7b2330fa59 References: #4600 Change-Id: I61e35bc93fe95610ae75b31c18a3282558cd4ffe 
References: #4600
Change-Id: I61e35bc93fe95610ae75b31c18a3282558cd4ffe
ensure pysqlite dialect enumerates correct isolation levels 2021-08-30T15:35:10+00:00 Mike Bayer mike_mp@zzzcomputing.com 2021-08-30T02:17:13+00:00 916bd20b6d1e7c153d334c31cf0882f502e3815e Fixed bug where the error message for SQLite invalid isolation level on the pysqlite driver would fail to indicate that "AUTOCOMMIT" is one of the valid isolation levels. Change-Id: Icbceab9a28af6a560859761fa92320b5473269a9 References: #6959 
Fixed bug where the error message for SQLite invalid isolation level on the
pysqlite driver would fail to indicate that "AUTOCOMMIT" is one of the
valid isolation levels.

Change-Id: Icbceab9a28af6a560859761fa92320b5473269a9
References: #6959
Replace all http:// links to https:// 2021-07-04T18:54:33+00:00 Federico Caselli cfederico87@gmail.com 2021-07-04T17:29:19+00:00 fb81f9c8d914f9911925dd3f4e77d7fc374b267c Also replace http://pypi.python.org/pypi with https://pypi.org/project Change-Id: I84b5005c39969a82140706472989f2a30b0c7685 
Also replace http://pypi.python.org/pypi with https://pypi.org/project

Change-Id: I84b5005c39969a82140706472989f2a30b0c7685
Pass URL object, not the string, to on_connect_url 2021-06-06T14:12:05+00:00 Mike Bayer mike_mp@zzzcomputing.com 2021-06-06T14:12:05+00:00 03633a6462ee16a1348acb98fe0323c74eb9ba85 The fix for pysqlcipher released in version 1.4.3 :ticket:`5848` was unfortunately non-working, in that the new ``on_connect_url`` hook was erroneously not receiving a ``URL`` object under normal usage of :func:`_sa.create_engine` and instead received a string that was unhandled; the test suite failed to fully set up the actual conditions under which this hook is called. This has been fixed. Fixes: #6586 Change-Id: I3bf738daec35877a10fdad740f08dca9e7420829 
The fix for pysqlcipher released in version 1.4.3 :ticket:`5848` was
unfortunately non-working, in that the new ``on_connect_url`` hook was
erroneously not receiving a ``URL`` object under normal usage of
:func:`_sa.create_engine` and instead received a string that was unhandled;
the test suite failed to fully set up the actual conditions under which
this hook is called. This has been fixed.

Fixes: #6586
Change-Id: I3bf738daec35877a10fdad740f08dca9e7420829
don't cache TypeDecorator by default 2021-05-06T17:57:43+00:00 Mike Bayer mike_mp@zzzcomputing.com 2021-05-06T16:24:00+00:00 6967b4502079e199b12f5eb307d10d27ec92d537 The :class:`.TypeDecorator` class will now emit a warning when used in SQL compilation with caching unless the ``.cache_ok`` flag is set to ``True`` or ``False``. ``.cache_ok`` indicates that all the parameters passed to the object are safe to be used as a cache key, ``False`` means they are not. Fixes: #6436 Change-Id: Ib1bb7dc4b124e38521d615c2e2e691e4915594fb 
The :class:`.TypeDecorator` class will now emit a warning when used in SQL
compilation with caching unless the ``.cache_ok`` flag is set to ``True``
or ``False``. ``.cache_ok`` indicates that all the parameters passed to the
object are safe to be used as a cache key, ``False`` means they are not.

Fixes: #6436
Change-Id: Ib1bb7dc4b124e38521d615c2e2e691e4915594fb