Bump sqlalchemy[asyncio] from 2.0.42 to 2.0.43
Type: Pull Request
State: Open
Association: Contributor
Comments: 0
(7 months ago)
(7 months ago)
dependencies python
Bumps sqlalchemy[asyncio] from 2.0.42 to 2.0.43.
Release notes
Sourced from sqlalchemy[asyncio]'s releases.
2.0.43
Released: August 11, 2025
orm
[orm] [bug] Fixed issue where using the
post_updatefeature would apply incorrect "pre-fetched" values to the ORM objects after a multi-row UPDATE process completed. These "pre-fetched" values would come from any column that had anColumn.onupdatecallable or a version id generator used byorm.Mapper.version_id_generator; for a version id generator that delivered random identifiers like timestamps or UUIDs, this incorrect data would lead to a DELETE statement against those same rows to fail in the next step.References: #12748
[orm] [bug] Fixed issue where
_orm.mapped_column.use_existing_columnparameter in_orm.mapped_column()would not work when the_orm.mapped_column()is used inside of anAnnotatedtype alias in polymorphic inheritance scenarios. The parameter is now properly recognized and processed during declarative mapping configuration.References: #12787
[orm] [bug] Improved the implementation of the
_orm.selectin_polymorphic()inheritance loader strategy to properly render the IN expressions using chunks of 500 records each, in the same manner as that of the_orm.selectinload()relationship loader strategy. Previously, the IN expression would be arbitrarily large, leading to failures on databases that have limits on the size of IN expressions including Oracle Database.References: #12790
engine
[engine] [usecase] Added new parameter
create_engine.skip_autocommit_rollbackwhich provides for a per-dialect feature of preventing the DBAPI.rollback()from being called under any circumstances, if the connection is detected as being in "autocommit" mode. This improves upon a critical performance issue identified in MySQL dialects where the network overhead of the.rollback()call remains prohibitive even if autocommit mode is set.References: #12784
postgresql
... (truncated)
Commits
- See full diff in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
Pull Request Statistics
1
1
+1
-1
Package Dependencies
Technical Details
| ID: | 4987603 |
| UUID: | 2737925205 |
| Node ID: | PR_kwDOLiB2fc6jMWxV |
| Host: | GitHub |
| Repository: | Azure-Samples/azure-postgres-pgvector-python |
| Merge State: | Unknown |