delta/python-packages/sqlalchemy.git/lib/sqlalchemy/testing/provision.py, branch rel_2_0_6 github.com: zzzeek/sqlalchemy.git Revert automatic set of sequence start to 1 2022-10-17T19:36:25+00:00 Federico Caselli cfederico87@gmail.com 2022-09-24T13:50:26+00:00 974b1bd0fc40e11fc2886b5a9fc333feeeebf546 The :class:`.Sequence` construct restores itself to the DDL behavior it had prior to the 1.4 series, where creating a :class:`.Sequence` with no additional arguments will emit a simple ``CREATE SEQUENCE`` instruction **without** any additional parameters for "start value". For most backends, this is how things worked previously in any case; **however**, for MS SQL Server, the default value on this database is ``-2**63``; to prevent this generally impractical default from taking effect on SQL Server, the :paramref:`.Sequence.start` parameter should be provided. As usage of :class:`.Sequence` is unusual for SQL Server which for many years has standardized on ``IDENTITY``, it is hoped that this change has minimal impact. Fixes: #7211 Change-Id: I1207ea10c8cb1528a1519a0fb3581d9621c27b31 
The :class:`.Sequence` construct restores itself to the DDL behavior it
had prior to the 1.4 series, where creating a :class:`.Sequence` with
no additional arguments will emit a simple ``CREATE SEQUENCE`` instruction
**without** any additional parameters for "start value".   For most backends,
this is how things worked previously in any case; **however**, for
MS SQL Server, the default value on this database is
``-2**63``; to prevent this generally impractical default
from taking effect on SQL Server, the :paramref:`.Sequence.start` parameter
should be provided.   As usage of :class:`.Sequence` is unusual
for SQL Server which for many years has standardized on ``IDENTITY``,
it is hoped that this change has minimal impact.

Fixes: #7211
Change-Id: I1207ea10c8cb1528a1519a0fb3581d9621c27b31
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
Tighten password security by removing `URL.__str__` 2022-09-23T21:27:30+00:00 Yassen Damyanov yd@itlabs.bg 2022-09-22T16:12:28+00:00 3333c6623fa45bcbc7fabd061184a79b7b7f2fa6 For improved security, the :class:`_url.URL` object will now use password obfuscation by default when ``str(url)`` is called. To stringify a URL with cleartext password, the :meth:`_url.URL.render_as_string` may be used, passing the :paramref:`_url.URL.render_as_string.hide_password` parameter as ``False``. Thanks to our contributors for this pull request. Fixes: #8567 Closes: #8563 Pull-request: https://github.com/sqlalchemy/sqlalchemy/pull/8563 Pull-request-sha: d1f1127f753849eb70b8d6cc64badf34e1b9219b Change-Id: If756c8073ff99ac83876d9833c8fe1d7c76211f9 
For improved security, the :class:`_url.URL` object will now use password
obfuscation by default when ``str(url)`` is called. To stringify a URL with
cleartext password, the :meth:`_url.URL.render_as_string` may be used,
passing the :paramref:`_url.URL.render_as_string.hide_password` parameter
as ``False``. Thanks to our contributors for this pull request.

Fixes: #8567
Closes: #8563
Pull-request: https://github.com/sqlalchemy/sqlalchemy/pull/8563
Pull-request-sha: d1f1127f753849eb70b8d6cc64badf34e1b9219b

Change-Id: If756c8073ff99ac83876d9833c8fe1d7c76211f9
Add ability to test using thick mode with oracledb 2022-06-20T18:41:48+00:00 Federico Caselli cfederico87@gmail.com 2022-06-20T18:41:48+00:00 e13e13421681768c300eab192cf2b150db9edaa6 Change-Id: Iee14750ba20422931bde4d61eaa570af482c7d8b References: #8147 
Change-Id: Iee14750ba20422931bde4d61eaa570af482c7d8b
References: #8147
rearchitect reflection for batched performance 2022-06-18T18:57:26+00:00 Federico Caselli cfederico87@gmail.com 2021-10-14T19:45:57+00:00 db08a699489c9b0259579d7ff7fd6bf3496ca3a2 Rearchitected the schema reflection API to allow some dialects to make use of high performing batch queries to reflect the schemas of many tables at once using much fewer queries. The new performance features are targeted first at the PostgreSQL and Oracle backends, and may be applied to any dialect that makes use of SELECT queries against system catalog tables to reflect tables (currently this omits the MySQL and SQLite dialects which instead make use of parsing the "CREATE TABLE" statement, however these dialects do not have a pre-existing performance issue with reflection. MS SQL Server is still a TODO). The new API is backwards compatible with the previous system, and should require no changes to third party dialects to retain compatibility; third party dialects can also opt into the new system by implementing batched queries for schema reflection. Along with this change is an updated reflection API that is fully :pep:`484` typed, features many new methods and some changes. Fixes: #4379 Change-Id: I897ec09843543aa7012bcdce758792ed3d415d08 
Rearchitected the schema reflection API to allow some dialects to make use
of high performing batch queries to reflect the schemas of many tables at
once using much fewer queries. The new performance features are targeted
first at the PostgreSQL and Oracle backends, and may be applied to any
dialect that makes use of SELECT queries against system catalog tables to
reflect tables (currently this omits the MySQL and SQLite dialects which
instead make use of parsing the "CREATE TABLE" statement, however these
dialects do not have a pre-existing performance issue with reflection. MS
SQL Server is still a TODO).

The new API is backwards compatible with the previous system, and should
require no changes to third party dialects to retain compatibility;
third party dialects can also opt into the new system by implementing
batched queries for schema reflection.

Along with this change is an updated reflection API that is fully
:pep:`484` typed, features many new methods and some changes.

Fixes: #4379
Change-Id: I897ec09843543aa7012bcdce758792ed3d415d08
Use tuple instead of raw url in string formatting (#7987) 2022-05-03T20:18:43+00:00 dzcode 9089037+dzcode@users.noreply.github.com 2022-05-03T20:18:43+00:00 675c3e17f7fcccb7534c46adb56529fc3ddd8dbf * Fixes: #7902 - Use tuple instead of raw url in string formatting * Fix lint error 
* Fixes: #7902 - Use tuple instead of raw url in string formatting

* Fix lint error
 inline mypy config; files ignoring type errors for the moment 2022-04-28T19:02:50+00:00 Mike Bayer mike_mp@zzzcomputing.com 2022-04-27T19:43:02+00:00 f2bd4f513628bb2a7a8e8b36383e3a4324eac803 to simplify pyproject.toml change the remaining files that aren't going to be typed on this first pass (unless of course someone wants to type some of these) to include # mypy: ignore-errors. for the moment, only a handful of ORM modules are to have more type checking implemented. It's important that ignore-errors is used and not "# type: ignore", as in the latter case, mypy doesn't even read the existing types in the file, which makes it impossible to type any files that refer to those modules at all. to simplify ongoing typing work use inline mypy config for remaining files that are "done" for now, indicating the level of type checking they currently have. Change-Id: I98669c1a305c2f0adba85d10b5425541f3fe9533 
to simplify pyproject.toml change the remaining files
that aren't going to be typed on this first pass
(unless of course someone wants to type some of these)
to include # mypy: ignore-errors.   for the moment, only a handful
of ORM modules are to have more type checking implemented.

It's important that ignore-errors is used and
not "# type: ignore", as in the latter case, mypy doesn't even
read the existing types in the file, which makes it impossible to
type any files that refer to those modules at all.

to simplify ongoing typing work use inline mypy config
for remaining files that are "done" for now, indicating the
level of type checking they currently have.

Change-Id: I98669c1a305c2f0adba85d10b5425541f3fe9533
pep-484 for sqlalchemy.event; use future annotations 2022-02-15T22:10:33+00:00 Mike Bayer mike_mp@zzzcomputing.com 2022-02-13T21:45:18+00:00 5c6081ddb03447697f909a03572b6d6d79e61b71 __future__.annotations mode allows us to use non-string annotations for argument and return types in most cases, but more importantly it removes a large amount of runtime overhead that would be spent in evaluating the annotations. Change-Id: I2f5b6126fe0019713fc50001be3627b664019ede References: #6810 
__future__.annotations mode allows us to use non-string
annotations for argument and return types in most cases,
but more importantly it removes a large amount of runtime
overhead that would be spent in evaluating the annotations.

Change-Id: I2f5b6126fe0019713fc50001be3627b664019ede
References: #6810
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