delta/python-packages/sqlalchemy.git/setup.cfg, 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
block asyncmy 0.2.6 2023-01-31T19:12:27+00:00 Mike Bayer mike_mp@zzzcomputing.com 2023-01-31T19:12:27+00:00 6d6a17240815b9090a2972607657f93d347167d6 The package seems fine but the wheels on the site are bad. Change-Id: I941eacbad880102788c0f6d285a212fc9178a385 References: https://github.com/long2ice/asyncmy/issues/48 
The package seems fine but the wheels on the site are bad.

Change-Id: I941eacbad880102788c0f6d285a212fc9178a385
References: https://github.com/long2ice/asyncmy/issues/48
Rewrite positional handling, test for "numeric" 2022-12-05T14:59:01+00:00 Federico Caselli cfederico87@gmail.com 2022-12-02T16:58:40+00:00 06c234d037bdab48e716d6c5f5dc200095269474 Changed how the positional compilation is performed. It's rendered by the compiler the same as the pyformat compilation. The string is then processed to replace the placeholders with the correct ones, and to obtain the correct order of the parameters. This vastly simplifies the computation of the order of the parameters, that in case of nested CTE is very hard to compute correctly. Reworked how numeric paramstyle behavers: - added support for repeated parameter, without duplicating them like in normal positional dialects - implement insertmany support. This requires that the dialect supports out of order placehoders, since all parameters that are not part of the VALUES clauses are placed at the beginning of the parameter tuple - support for different identifiers for a numeric parameter. It's for example possible to use postgresql style placeholder $1, $2, etc Added two new dialect based on sqlite to test "numeric" fully using both :1 style and $1 style. Includes a workaround for SQLite's not-really-correct numeric implementation. Changed parmstyle of asyncpg dialect to use numeric, rendering with its native $ identifiers Fixes: #8926 Fixes: #8849 Change-Id: I7c640467d49adfe6d795cc84296fc7403dcad4d6 
Changed how the positional compilation is performed. It's rendered by the compiler
the same as the pyformat compilation. The string is then processed to replace
the placeholders with the correct ones, and to obtain the correct order of the
parameters.
This vastly simplifies the computation of the order of the parameters, that in
case of nested CTE is very hard to compute correctly.

Reworked how numeric paramstyle behavers:
- added support for repeated parameter, without duplicating them like in normal
positional dialects
- implement insertmany support. This requires that the dialect supports out of
order placehoders, since all parameters that are not part of the VALUES clauses
are placed at the beginning of the parameter tuple
- support for different identifiers for a numeric parameter. It's for example
possible to use postgresql style placeholder $1, $2, etc

Added two new dialect based on sqlite to test "numeric" fully using
both :1 style and $1 style. Includes a workaround for SQLite's
not-really-correct numeric implementation.

Changed parmstyle of asyncpg dialect to use numeric, rendering with its native
$ identifiers

Fixes: #8926
Fixes: #8849
Change-Id: I7c640467d49adfe6d795cc84296fc7403dcad4d6
block mariadb-connector 1.1.5 2022-11-07T19:43:39+00:00 Mike Bayer mike_mp@zzzcomputing.com 2022-11-07T19:43:39+00:00 9056dc02178905fb901da5c182618fb593331592 package is not installable See https://jira.mariadb.org/browse/MCOL-5298 Change-Id: I278a1831f379c2c17a1b87dd4c8b3a5b5b585e6d 
package is not installable

See https://jira.mariadb.org/browse/MCOL-5298

Change-Id: I278a1831f379c2c17a1b87dd4c8b3a5b5b585e6d
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
add python 3.11 to supported versions 2022-10-16T14:09:20+00:00 Mike Bayer mike_mp@zzzcomputing.com 2022-10-16T14:09:20+00:00 7fd8898b10669c8e6b08c5d66c92bdc975aaa353 Change-Id: Ibf699297b12c1c72c570db380282e97adfdef2b9 
Change-Id: Ibf699297b12c1c72c570db380282e97adfdef2b9
block mariadb 1.1.2 2022-06-28T14:18:58+00:00 Mike Bayer mike_mp@zzzcomputing.com 2022-06-28T14:18:58+00:00 f19e50ab75cfc904acef31434c92542f3ab50d61 regression causing unicode schema queries to fail Change-Id: Ie66ca038357ec90804a357979d4fd22611c47340 References: https://jira.mariadb.org/browse/CONPY-209 
regression causing unicode schema queries to fail

Change-Id: Ie66ca038357ec90804a357979d4fd22611c47340
References: https://jira.mariadb.org/browse/CONPY-209
use license_files instead of the deprecated license_file 2022-06-27T20:25:26+00:00 Federico Caselli cfederico87@gmail.com 2022-06-27T20:25:26+00:00 36e5eaeff42a39142b7894742add88116c453969 Change-Id: I787370bd0c912c2216b2f3efceb487a2ab6a4ddb 
Change-Id: I787370bd0c912c2216b2f3efceb487a2ab6a4ddb
always use typing_extension 2022-06-25T09:55:07+00:00 Federico Caselli cfederico87@gmail.com 2022-06-25T09:55:07+00:00 53d7f6be9b05efc6f4c8c8682c72dd59a4baf523 always use typing_extensions to import missing types in old python version Change-Id: Ied03e8597e10bfae06f0e37d8624fbad90e74bcf 
always use typing_extensions to import missing types in old python version

Change-Id: Ied03e8597e10bfae06f0e37d8624fbad90e74bcf
Merge "rearchitect reflection for batched performance" into main 2022-06-18T21:08:27+00:00 Federico Caselli cfederico87@gmail.com 2022-06-18T21:08:27+00:00 be576e7d88b6038781e52f7ef79799dbad09cd54