Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Bump sqlalchemy from 2.0.28 to 2.0.29 (#198)
Bumps [sqlalchemy](https://github.com/sqlalchemy/sqlalchemy) from 2.0.28 to 2.0.29. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/sqlalchemy/sqlalchemy/releases">sqlalchemy's releases</a>.</em></p> <blockquote> <h1>2.0.29</h1> <p>Released: March 23, 2024</p> <h2>orm</h2> <ul> <li> <p><strong>[orm] [usecase]</strong> Added support for the <a href="https://peps.python.org/pep-0695">PEP 695</a> <code>TypeAliasType</code> construct as well as the python 3.12 native <code>type</code> keyword to work with ORM Annotated Declarative form when using these constructs to link to a <a href="https://peps.python.org/pep-0593">PEP 593</a> <code>Annotated</code> container, allowing the resolution of the <code>Annotated</code> to proceed when these constructs are used in a <code>_orm.Mapped</code> typing container.</p> <p>References: <a href="https://www.sqlalchemy.org/trac/ticket/11130">#11130</a></p> </li> <li> <p><strong>[orm] [bug]</strong> Fixed Declarative issue where typing a relationship using <code>_orm.Relationship</code> rather than <code>_orm.Mapped</code> would inadvertently pull in the "dynamic" relationship loader strategy for that attribute.</p> <p>References: <a href="https://www.sqlalchemy.org/trac/ticket/10611">#10611</a></p> </li> <li> <p><strong>[orm] [bug]</strong> Fixed issue in ORM annotated declarative where using <code>_orm.mapped_column()</code> with an <code>_orm.mapped_column.index</code> or <code>_orm.mapped_column.unique</code> setting of False would be overridden by an incoming <code>Annotated</code> element that featured that parameter set to <code>True</code>, even though the immediate <code>_orm.mapped_column()</code> element is more specific and should take precedence. The logic to reconcile the booleans has been enhanced to accommodate a local value of <code>False</code> as still taking precedence over an incoming <code>True</code> value from the annotated element.</p> <p>References: <a href="https://www.sqlalchemy.org/trac/ticket/11091">#11091</a></p> </li> <li> <p><strong>[orm] [bug] [regression]</strong> Fixed regression from version 2.0.28 caused by the fix for <a href="https://www.sqlalchemy.org/trac/ticket/11085">#11085</a> where the newer method of adjusting post-cache bound parameter values would interefere with the implementation for the <code>_orm.subqueryload()</code> loader option, which has some more legacy patterns in use internally, when the additional loader criteria feature were used with this loader option.</p> <p>References: <a href="https://www.sqlalchemy.org/trac/ticket/11173">#11173</a></p> </li> </ul> <h2>engine</h2> <ul> <li><strong>[engine] [bug]</strong> Fixed issue in <code>engine_insertmanyvalues</code> feature where using a primary key column with an "inline execute" default generator such as an explicit <code>Sequence</code> with an explcit schema name, while at the same time using the <code>_engine.Connection.execution_options.schema_translate_map</code></li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/sqlalchemy/sqlalchemy/commits">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will 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 version` will 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 dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details>
- Loading branch information
