delta/python-packages/sqlalchemy.git/lib/sqlalchemy/testing/requirements.py, branch rel_2_0_6 github.com: zzzeek/sqlalchemy.git audition pymssql once more; retire sane_rowcount_returning 2023-03-05T04:22:20+00:00 Mike Bayer mike_mp@zzzcomputing.com 2023-03-03T14:30:58+00:00 b38fb59fe484d6e4e5992c9b2dc9b9f7724f016a pymssql seems to be maintained again and seems to be working completely, so let's try re-enabling it. Fixed issue in the new :class:`.Uuid` datatype which prevented it from working with the pymssql driver. As pymssql seems to be maintained again, restored testing support for pymssql. Tweaked the pymssql dialect to take better advantage of RETURNING for INSERT statements in order to retrieve last inserted primary key values, in the same way as occurs for the mssql+pyodbc dialect right now. Identified that the ``sqlite`` and ``mssql+pyodbc`` dialects are now compatible with the SQLAlchemy ORM's "versioned rows" feature, since SQLAlchemy now computes rowcount for a RETURNING statement in this specific case by counting the rows returned, rather than relying upon ``cursor.rowcount``. In particular, the ORM versioned rows use case (documented at :ref:`mapper_version_counter`) should now be fully supported with the SQL Server pyodbc dialect. Change-Id: I38a0666587212327aecf8f98e86031ab25d1f14d References: #5321 Fixes: #9414 
pymssql seems to be maintained again and seems to be working
completely, so let's try re-enabling it.

Fixed issue in the new :class:`.Uuid` datatype which prevented it from
working with the pymssql driver. As pymssql seems to be maintained again,
restored testing support for pymssql.

Tweaked the pymssql dialect to take better advantage of
RETURNING for INSERT statements in order to retrieve last inserted primary
key values, in the same way as occurs for the mssql+pyodbc dialect right
now.

Identified that the ``sqlite`` and ``mssql+pyodbc`` dialects are now
compatible with the SQLAlchemy ORM's "versioned rows" feature, since
SQLAlchemy now computes rowcount for a RETURNING statement in this specific
case by counting the rows returned, rather than relying upon
``cursor.rowcount``.  In particular, the ORM versioned rows use case
(documented at :ref:`mapper_version_counter`) should now be fully
supported with the SQL Server pyodbc dialect.

Change-Id: I38a0666587212327aecf8f98e86031ab25d1f14d
References: #5321
Fixes: #9414
prevent float tests from running on asyncmy 2023-02-15T23:28:12+00:00 Mike Bayer mike_mp@zzzcomputing.com 2023-02-15T23:28:12+00:00 8855656626202e541bd2c95bc023e820a022322f asyncmy 0.2.7 has had a loss in float precision for even very low numbers of significant digits. Change-Id: Iec6d2650943eeaa8e854f21990f6565d73331f8c References: https://github.com/long2ice/asyncmy/issues/56 
asyncmy 0.2.7 has had a loss in float precision for even
very low numbers of significant digits.

Change-Id: Iec6d2650943eeaa8e854f21990f6565d73331f8c
References: https://github.com/long2ice/asyncmy/issues/56
happy new year 2023 2023-01-03T17:45:52+00:00 Mike Bayer mike_mp@zzzcomputing.com 2023-01-03T17:45:52+00:00 5147bf8e3cb321b8728b3af5bb0b2644995b3793 Change-Id: I625af65b3fb1815b1af17dc2ef47dd697fdc3fb1 
Change-Id: I625af65b3fb1815b1af17dc2ef47dd697fdc3fb1
add exclusion for unusual chars in column names 2022-12-19T13:35:53+00:00 Mike Bayer mike_mp@zzzcomputing.com 2022-12-19T13:34:51+00:00 946058ec6070ab4db9fdfab612ec4543fea9cd1c Added new exclusion rule for third party dialects called ``unusual_column_name_characters``, which can be "closed" for third party dialects that don't support column names with unusual characters such as dots, slashes, or percent signs in them, even if the name is properly quoted. Fixes: #9002 Change-Id: I44b765df4c73ce5ec1907d031fd9c89761fd99d1 References: #8993 
Added new exclusion rule for third party dialects called
``unusual_column_name_characters``, which can be "closed" for third party
dialects that don't support column names with unusual characters such as
dots, slashes, or percent signs in them, even if the name is properly
quoted.

Fixes: #9002
Change-Id: I44b765df4c73ce5ec1907d031fd9c89761fd99d1
References: #8993
Repair test in 32bit python builds. 2022-11-12T19:15:26+00:00 Federico Caselli cfederico87@gmail.com 2022-11-12T19:15:26+00:00 9f4ac8d155f58b59cf314cfbc73195ed51a0c146 Change-Id: I8287f3e1a975534c8a01a41c9dcc7e5e9f08bb52 
Change-Id: I8287f3e1a975534c8a01a41c9dcc7e5e9f08bb52
repair --disable-asyncio parameter 2022-11-11T16:20:34+00:00 Mike Bayer mike_mp@zzzcomputing.com 2022-11-11T14:46:06+00:00 604611e7e522269ee11b314fb6fb75873a465494 Fixed issue where the ``--disable-asyncio`` parameter to the test suite would fail to not actually run greenlet tests and would also not prevent the suite from using a "wrapping" greenlet for the whole suite. This parameter now ensures that no greenlet or asyncio use will occur within the entire run when set. Fixes: #8793 Change-Id: I87b510846b2cc24413cd54e7b7136e91aad3c309 
Fixed issue where the ``--disable-asyncio`` parameter to the test suite
would fail to not actually run greenlet tests and would also not prevent
the suite from using a "wrapping" greenlet for the whole suite. This
parameter now ensures that no greenlet or asyncio use will occur within the
entire run when set.

Fixes: #8793
Change-Id: I87b510846b2cc24413cd54e7b7136e91aad3c309
Improve typings of execution options 2022-11-03T01:38:31+00:00 Federico Caselli cfederico87@gmail.com 2022-10-17T20:02:13+00:00 d10b62f54e6b9dd0613c0412b924c1b346ec1611 Fixes: #8605 Change-Id: I4aec83b9f321462427c3f4ac941c3b272255c088 
Fixes: #8605
Change-Id: I4aec83b9f321462427c3f4ac941c3b272255c088
use only object_id() function for temp tables 2022-10-28T13:08:49+00:00 Mike Barry michael.barry@gmo.com 2022-10-26T17:40:32+00:00 59f2d0c96152128d8e02e43dcda045593153c86e Fixed issue with :meth:`.Inspector.has_table` when used against a temporary table for the SQL Server dialect would fail an invalid object name error on some Azure variants, due to an unnecessary information schema query that is not supported on those server versions. Pull request courtesy Mike Barry. the patch also fills out test support for has_table() against temp tables, temp views, adding to the has_table() support just added for views in #8700. Fixes: #8714 Closes: #8716 Pull-request: https://github.com/sqlalchemy/sqlalchemy/pull/8716 Pull-request-sha: e2ac7a52e2b09a349a703ba1e1a2911f4d3c0912 Change-Id: Ia73e4e9e977a2d6b7e100abd2f81a8c8777dc9bb 
Fixed issue with :meth:`.Inspector.has_table` when used against a temporary
table for the SQL Server dialect would fail an invalid object name error on
some Azure variants, due to an unnecessary information schema query that is
not supported on those server versions. Pull request courtesy Mike Barry.

the patch also fills out test support for has_table()
against temp tables, temp views, adding to the has_table() support just
added for views in #8700.

Fixes: #8714
Closes: #8716
Pull-request: https://github.com/sqlalchemy/sqlalchemy/pull/8716
Pull-request-sha: e2ac7a52e2b09a349a703ba1e1a2911f4d3c0912

Change-Id: Ia73e4e9e977a2d6b7e100abd2f81a8c8777dc9bb
New ORM Query Guide featuring DML support 2022-09-25T23:38:10+00:00 Mike Bayer mike_mp@zzzcomputing.com 2022-08-18T17:56:50+00:00 81d8394c0b5342cdc603cb2e07e12139c9506bf6 reviewers: these docs publish periodically at: https://docs.sqlalchemy.org/en/gerrit/4042/orm/queryguide/index.html See the "last generated" timestamp near the bottom of the page to ensure the latest version is up Change includes some other adjustments: * small typing fixes for end-user benefit * removal of a bunch of old examples for patterns that nobody uses or aren't really what we promote now * modernization of some examples, including inheritance Change-Id: I9929daab7797be9515f71c888b28af1209e789ff 
reviewers:  these docs publish periodically at:
https://docs.sqlalchemy.org/en/gerrit/4042/orm/queryguide/index.html

See the "last generated" timestamp near the bottom of the
page to ensure the latest version is up

Change includes some other adjustments:

* small typing fixes for end-user benefit
* removal of a bunch of old examples for patterns that nobody
  uses or aren't really what we promote now
* modernization of some examples, including inheritance

Change-Id: I9929daab7797be9515f71c888b28af1209e789ff
implement batched INSERT..VALUES () () for executemany 2022-09-24T15:15:32+00:00 Mike Bayer mike_mp@zzzcomputing.com 2022-07-18T19:08:37+00:00 2bcc97da424eef7db9a5d02f81d02344925415ee the feature is enabled for all built in backends when RETURNING is used, except for Oracle that doesn't need it, and on psycopg2 and mssql+pyodbc it is used for all INSERT statements, not just those that use RETURNING. third party dialects would need to opt in to the new feature by setting use_insertmanyvalues to True. Also adds dialect-level guards against using returning with executemany where we dont have an implementation to suit it. execute single w/ returning still defers to the server without us checking. Fixes: #6047 Fixes: #7907 Change-Id: I3936d3c00003f02e322f2e43fb949d0e6e568304 
the feature is enabled for all built in backends
when RETURNING is used,
except for Oracle that doesn't need it,  and on
psycopg2 and mssql+pyodbc it is used for all INSERT statements,
not just those that use RETURNING.

third party dialects would need to opt in to the new feature
by setting use_insertmanyvalues to True.

Also adds dialect-level guards against using returning
with executemany where we dont have an implementation to
suit it.   execute single w/ returning still defers to the
server without us checking.

Fixes: #6047
Fixes: #7907
Change-Id: I3936d3c00003f02e322f2e43fb949d0e6e568304