summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* add subfolder to the zip file, add workflow dispatchworkflow_test_doc_buildFederico Caselli2023-04-241-2/+4
| | | | Change-Id: I32d8e2019c94b067d0298c5e303e5fd678946471
* remove ./ from tar archiveFederico Caselli2023-04-241-1/+1
| | | | Change-Id: I59a2d2699dd19568be71cba5a4aed4e155b5a2e1
* improve zip/tar generationFederico Caselli2023-04-241-3/+5
| | | | Change-Id: Ib9c9104d945a916df2fd2dcab523d23785693a42
* try again againFederico Caselli2023-04-241-2/+2
| | | | Change-Id: I8988a644f63133dcf8877f0c7f79ce35585a124f
* try againFederico Caselli2023-04-241-19/+6
| | | | Change-Id: I134879f35dbc44548342634fa4f83a80d3ed0df5
* do commands in run run concurrently (how does cd work then?)Mike Bayer2023-04-241-2/+5
| | | | Change-Id: Ida158e1528cc3f2b81611aef50d2c87a85b9a5a3
* try to make a real site build + zip buildMike Bayer2023-04-241-8/+27
| | | | Change-Id: Ide8e15bacb823b5f7a9aae21cd0b871294556b7d
* try sphinx 6Federico Caselli2023-04-231-0/+1
| | | | Change-Id: Ib2e2c1e065a58575a10571a5f59fe3a51c88eed7
* Add workflow to build docsFederico Caselli2023-04-231-0/+50
| | | | Change-Id: I3f5ad6f3832ea56aba72c62f6bd2092288dcb5c9
* :pencil2: Fix repetition for same reference page on documentation (#9694)HoonCheol Shin2023-04-231-3/+2
| | | | | * :pencil2: remove repeat for same reference * :pencil2: apply the suggestion from @zzzeek
* repair large_resultsetsMike Bayer2023-04-221-2/+16
| | | | | | this is ahead of https://gerrit.sqlalchemy.org/c/sqlalchemy/sqlalchemy/+/4581/ Change-Id: If8a36e457bdb62ddca04e39bb4c1288d4fa53c20
* support slice access for .cMike Bayer2023-04-224-5/+59
| | | | | | | | | | | | Added support for slice access with :class:`.ColumnCollection`, e.g. ``table.c[0:5]``, ``subquery.c[:-1]`` etc. Slice access returns a sub :class:`.ColumnCollection` in the same way as passing a tuple of keys. This is a natural continuation of the key-tuple access added for :ticket:`8285`, which it appears to be an oversight that this usage was omitted. Change-Id: I6378642f39501ffbbae4acadf1dc38a43c39d722 References: #8285 References: #9690
* Version 2.0.11 placeholderMike Bayer2023-04-212-1/+5
|
* - 2.0.10rel_2_0_10Mike Bayer2023-04-2116-190/+204
|
* restore fallback for uow testMike Bayer2023-04-211-0/+9
| | | | | | | | | in cf6872d3bdf1a8a9613e85369 I decided this test should be able to run in all cases, however apparently on windows / py37 on GH actions something goes wrong, so restore the skip to that case. Change-Id: Iaf4db313c20ce30469032af930b7dc86417d0705
* changelog fixes; editsMike Bayer2023-04-217-16/+19
| | | | Change-Id: I6bbef2416f864d1414d56f9bf39026156aed5e67
* Merge "Add name_func optional attribute for asyncpg adapter" into mainFederico Caselli2023-04-213-3/+97
|\
| * Add name_func optional attribute for asyncpg adapterPavel Sirotkin2023-04-213-3/+97
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | I faced an issue related to pg bouncer and prepared statement cache flow in asyncpg dialect. Regarding this discussion https://github.com/sqlalchemy/sqlalchemy/issues/6467 I prepared PR to support an optional parameter `name` in prepared statement which is allowed, since 0.25.0 version in `asyncpg` https://github.com/MagicStack/asyncpg/pull/846 **UPD:** the issue with proposal: https://github.com/sqlalchemy/sqlalchemy/issues/9608 ### Description Added optional parameter `name_func` to `AsyncAdapt_asyncpg_connection` class which will call on the `self._connection.prepare()` function and populate a unique name. so in general instead this ```python from uuid import uuid4 from asyncpg import Connection class CConnection(Connection): def _get_unique_id(self, prefix: str) -> str: return f'__asyncpg_{prefix}_{uuid4()}__' engine = create_async_engine(..., connect_args={ 'connection_class': CConnection, }, ) ``` would be enough ```python from uuid import uuid4 engine = create_async_engine(..., connect_args={ 'name_func': lambda: f'__asyncpg_{uuid4()}__', }, ) ``` ### Checklist <!-- go over following points. check them with an `x` if they do apply, (they turn into clickable checkboxes once the PR is submitted, so no need to do everything at once) --> This pull request is: - [ ] A documentation / typographical error fix - Good to go, no issue or tests are needed - [ ] A short code fix - please include the issue number, and create an issue if none exists, which must include a complete example of the issue. one line code fixes without an issue and demonstration will not be accepted. - Please include: `Fixes: #<issue number>` in the commit message - please include tests. one line code fixes without tests will not be accepted. - [x] A new feature implementation - please include the issue number, and create an issue if none exists, which must include a complete example of how the feature would look. - Please include: `Fixes: #<issue number>` in the commit message - please include tests. **Have a nice day!** Fixes: #9608 Closes: #9607 Pull-request: https://github.com/sqlalchemy/sqlalchemy/pull/9607 Pull-request-sha: b4bc8d3e57ab095a26112830ad4bea36083454e3 Change-Id: Icd753366cba166b8a60d1c8566377ec8335cd828
* | Merge "add deterministic imv returning ordering using sentinel columns" into ↵mike bayer2023-04-2171-660/+5266
|\ \ | | | | | | | | | main
| * | add deterministic imv returning ordering using sentinel columnsMike Bayer2023-04-2171-660/+5266
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Repaired a major shortcoming which was identified in the :ref:`engine_insertmanyvalues` performance optimization feature first introduced in the 2.0 series. This was a continuation of the change in 2.0.9 which disabled the SQL Server version of the feature due to a reliance in the ORM on apparent row ordering that is not guaranteed to take place. The fix applies new logic to all "insertmanyvalues" operations, which takes effect when a new parameter :paramref:`_dml.Insert.returning.sort_by_parameter_order` on the :meth:`_dml.Insert.returning` or :meth:`_dml.UpdateBase.return_defaults` methods, that through a combination of alternate SQL forms, direct correspondence of client side parameters, and in some cases downgrading to running row-at-a-time, will apply sorting to each batch of returned rows using correspondence to primary key or other unique values in each row which can be correlated to the input data. Performance impact is expected to be minimal as nearly all common primary key scenarios are suitable for parameter-ordered batching to be achieved for all backends other than SQLite, while "row-at-a-time" mode operates with a bare minimum of Python overhead compared to the very heavyweight approaches used in the 1.x series. For SQLite, there is no difference in performance when "row-at-a-time" mode is used. It's anticipated that with an efficient "row-at-a-time" INSERT with RETURNING batching capability, the "insertmanyvalues" feature can be later be more easily generalized to third party backends that include RETURNING support but not necessarily easy ways to guarantee a correspondence with parameter order. Fixes: #9618 References: #9603 Change-Id: I1d79353f5f19638f752936ba1c35e4dc235a8b7c
* | | Merge "try to omit unnecessary cols for ORM bulk insert + returning" into mainmike bayer2023-04-214-30/+93
|\ \ \ | |/ /
| * | try to omit unnecessary cols for ORM bulk insert + returningMike Bayer2023-04-214-30/+93
| | | | | | | | | | | | | | | | | | | | | | | | | | | Fixed bug in ORM bulk insert feature where additional unnecessary columns would be rendered in the INSERT statement if RETURNING of individual columns were requested. Fixes: #9685 Change-Id: Ibf5f06ab017215c7c9bd8850c3a006f73fe78c68
* | | Merge "Add intersection method to Range class" into mainmike bayer2023-04-213-0/+96
|\ \ \
| * | | Add intersection method to Range classYurii Karabas2023-04-143-0/+96
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <!-- Provide a general summary of your proposed changes in the Title field above --> ### Description Fixes: #9509 <!-- Describe your changes in detail --> ### Checklist <!-- go over following points. check them with an `x` if they do apply, (they turn into clickable checkboxes once the PR is submitted, so no need to do everything at once) --> This pull request is: - [ ] A documentation / typographical error fix - Good to go, no issue or tests are needed - [ ] A short code fix - please include the issue number, and create an issue if none exists, which must include a complete example of the issue. one line code fixes without an issue and demonstration will not be accepted. - Please include: `Fixes: #<issue number>` in the commit message - please include tests. one line code fixes without tests will not be accepted. - [x] A new feature implementation - please include the issue number, and create an issue if none exists, which must include a complete example of how the feature would look. - Please include: `Fixes: #<issue number>` in the commit message - please include tests. **Have a nice day!** Closes: #9510 Pull-request: https://github.com/sqlalchemy/sqlalchemy/pull/9510 Pull-request-sha: 596648e7989327eef1807057519b2295b48f1adf Change-Id: I7b527edda09eb78dee6948edd4d49b00ea437011
* | | | fix typo ('resemblence' -> 'resemblance') (#9674)Tim Stewart2023-04-201-5/+1
| |_|/ |/| |
* | | Bump pypa/cibuildwheel from 2.12.1 to 2.12.3 (#9672)dependabot[bot]2023-04-191-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Bumps [pypa/cibuildwheel](https://github.com/pypa/cibuildwheel) from 2.12.1 to 2.12.3. - [Release notes](https://github.com/pypa/cibuildwheel/releases) - [Changelog](https://github.com/pypa/cibuildwheel/blob/main/docs/changelog.md) - [Commits](https://github.com/pypa/cibuildwheel/compare/v2.12.1...v2.12.3) --- updated-dependencies: - dependency-name: pypa/cibuildwheel dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
* | | Merge "Define type hints for remaining column operators" into mainFederico Caselli2023-04-183-17/+104
|\ \ \
| * | | Define type hints for remaining column operatorsMartijn Pieters2023-04-183-17/+104
| | |/ | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Added typing information for recently added operators :meth:`.ColumnOperators.icontains`, :meth:`.ColumnOperators.istartswith`, :meth:`.ColumnOperators.iendswith`, and bitwise operators :meth:`.ColumnOperators.bitwise_and`, :meth:`.ColumnOperators.bitwise_or`, :meth:`.ColumnOperators.bitwise_xor`, :meth:`.ColumnOperators.bitwise_not`, :meth:`.ColumnOperators.bitwise_lshift` :meth:`.ColumnOperators.bitwise_rshift`. Pull request courtesy Martijn Pieters. Fixes: #9650 Closes: #9652 Pull-request: https://github.com/sqlalchemy/sqlalchemy/pull/9652 Pull-request-sha: 005c56848af8cff6bb19f71541873027f141eb6e Change-Id: I2fa06eb42ce668df9d9c760d233906f87484dd12
* | | improve return type for QueryableAttribute.and_()Mike Bayer2023-04-183-1/+46
|/ / | | | | | | | | | | | | | | | | Fixed typing issue where :meth:`_orm.PropComparator.and_` expressions would not be correctly typed inside of loader options such as :func:`_orm.selectinload`. Fixes: #9669 Change-Id: I874cb22c004e0a24f2b7f530fda542de2c4c6d3b
* | Merge "apply criteria options from top-level core-only statement" into mainmike bayer2023-04-174-35/+315
|\ \
| * | apply criteria options from top-level core-only statementMike Bayer2023-04-174-35/+315
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Made an improvement to the :func:`_orm.with_loader_criteria` loader option to allow it to be indicated in the :meth:`.Executable.options` method of a top-level statement that is not itself an ORM statement. Examples include :func:`_sql.select` that's embedded in compound statements such as :func:`_sql.union`, within an :meth:`_dml.Insert.from_select` construct, as well as within CTE expressions that are not ORM related at the top level. Improved propagation of :func:`_orm.with_loader_criteria` within ORM enabled UPDATE and DELETE statements as well. Fixes: #9635 Change-Id: I088ad91929dc797c06f292f5dc547d48ffb30430
* | | dont assume _compile_options are presentMike Bayer2023-04-173-1/+48
|/ / | | | | | | | | | | | | | | | | | | | | | | Fixed bug where various ORM-specific getters such as :attr:`.ORMExecuteState.is_column_load`, :attr:`.ORMExecuteState.is_relationship_load`, :attr:`.ORMExecuteState.loader_strategy_path` etc. would throw an ``AttributeError`` if the SQL statement itself were a "compound select" such as a UNION. Fixes: #9634 Change-Id: Ia37df5d6f89d6534d69237dcab294bd849ece28b
* | run docs syncMike Bayer2023-04-171-13/+11
| | | | | | | | | | | | this is needed due to previous commit f7bfa04bcae1e9baf Change-Id: I7fa397707a018455a2c96b62704dfd506742b0cd
* | clarify get_isolation_level() excludes AUTOCOMMITMike Bayer2023-04-171-30/+35
|/ | | | | | | I thought this was documented but apparently not. Fixes: #9658 Change-Id: I93fad12c159c599ffdbab1aff586b49e8c92a6e4
* Remove mypy dataclass reference (#9651)Federico Caselli2023-04-141-15/+0
|
* Merge "Add additional seealso to schema reflect parameters" into mainmike bayer2023-04-131-0/+19
|\
| * Add additional seealso to schema reflect parametersFederico Caselli2023-04-131-0/+19
| | | | | | | | | | References: #9606 Change-Id: I1213f881621a80eb78a2db84e53150437144f26c
* | Merge "Add pool creation functions" into mainmike bayer2023-04-1312-13/+194
|\ \ | |/ |/|
| * Add pool creation functionsFederico Caselli2023-04-1212-13/+194
| | | | | | | | | | | | | | | | | | | | Added :func:`_sa.create_pool_from_url` and :func:`_asyncio.create_async_pool_from_url` to create a :class:`_pool.Pool` instance from an input url passed as string or :class:`_sa.URL`. Fixes: #9613 Change-Id: Icd8aa3f2849e6fd1bc5341114f3ef8d216a2c543
* | Merge "Remove old versionadded and versionchanged" into mainmike bayer2023-04-1263-709/+4
|\ \
| * | Remove old versionadded and versionchangedFederico Caselli2023-04-1263-709/+4
| |/ | | | | | | | | | | | | Removed versionadded and versionchanged for version prior to 1.2 since they are no longer useful. Change-Id: I5c53d1188bc5fec3ab4be39ef761650ed8fa6d3e
* | Merge "establish column_property and query_expression as readonly from a dc ↵Federico Caselli2023-04-1216-97/+407
|\ \ | |/ |/| | | perspective" into main
| * establish column_property and query_expression as readonly from a dc perspectiveMike Bayer2023-04-1216-97/+407
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fixed bug in ORM Declarative Dataclasses where the :func:`_orm.queryable_attribute` and :func:`_orm.column_property` constructs, which are documented as read-only constructs in the context of a Declarative mapping, could not be used with a :class:`_orm.MappedAsDataclass` class without adding ``init=False``, which in the case of :func:`_orm.queryable_attribute` was not possible as no ``init`` parameter was included. These constructs have been modified from a dataclass perspective to be assumed to be "read only", setting ``init=False`` by default and no longer including them in the pep-681 constructor. The dataclass parameters for :func:`_orm.column_property` ``init``, ``default``, ``default_factory``, ``kw_only`` are now deprecated; these fields don't apply to :func:`_orm.column_property` as used in a Declarative dataclasses configuration where the construct would be read-only. Also added read-specific parameter :paramref:`_orm.queryable_attribute.compare` to :func:`_orm.queryable_attribute`; :paramref:`_orm.queryable_attribute.repr` was already present. Added missing :paramref:`_orm.mapped_column.active_history` parameter to :func:`_orm.mapped_column` construct. Fixes: #9628 Change-Id: I2ab44d6b763b20410bd1ebb5ac949a6d223f1ce2
* | make the linter happyFederico Caselli2023-04-121-3/+1
| | | | | | | | Change-Id: I7104c7cb081c9b61894958cef5d0b4707474994d
* | Fix Association Proxy exampleGord Thompson2023-04-111-1/+4
|/ | | | | | | | Minor corrections to "Simplifying Association Objects" example in the Association Proxy docs. https: //github.com/sqlalchemy/sqlalchemy/discussions/9636 Change-Id: Ib433cf78b149d330889d947bbaf2b03c9dd87c29
* restore mypy to released version 1.2.0Mike Bayer2023-04-101-2/+1
| | | | Change-Id: Ice0233af37f387747a283ef2d2293aaa194b52d9
* Merge "include declared_directive as a declared_attr" into mainmike bayer2023-04-103-2/+52
|\
| * include declared_directive as a declared_attrMike Bayer2023-04-103-2/+52
| | | | | | | | | | | | | | | | | | | | | | Fixed issue where the :meth:`_orm.declared_attr.directive` modifier was not correctly honored for subclasses when applied to the ``__mapper_args__`` special method name, as opposed to direct use of :class:`_orm.declared_attr`. The two constructs should have identical runtime behaviors. Fixes: #9625 Change-Id: I0dfe9e73bb45f70dbebc8e94ce280ad3b52e867f
* | Merge "mypy 1.2 has fixed dataclass descriptor support" into mainmike bayer2023-04-103-44/+38
|\ \ | |/ |/|
| * mypy 1.2 has fixed dataclass descriptor supportMike Bayer2023-04-043-44/+38
| | | | | | | | | | | | | | Currently using the PR for test. Change-Id: Idc4c475587f5151ef79046d24ca3ac274c2cb2ca References: https://github.com/python/mypy/issues/14868