[PR #81] [MERGED] Scheduled weekly dependency update for week 04 #121

New issue

Closed

opened 2026-02-26 01:33:17 +03:00 by kerem · 0 comments

kerem commented

2026-02-26 01:33:17 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/jeffknupp/sandman2/pull/81
Author: @pyup-bot
Created: 1/28/2019
Status: ✅ Merged
Merged: 1/28/2019
Merged by: @jeffknupp

Base: master ← Head: pyup-scheduled-update-2019-01-28

📝 Commits (1)

8e720a6 Update sqlalchemy from 1.2.16 to 1.2.17

📊 Changes

1 file changed (+1 additions, -1 deletions)

View changed files

📝 requirements.txt (+1 -1)

📄 Description

Update SQLAlchemy from 1.2.16 to 1.2.17.

Changelog

1.2.17

:released: January 25, 2019

 .. change::
    :tags: feature, orm
    :tickets: 4461

    Added new event hooks :meth:`.QueryEvents.before_compile_update` and
    :meth:`.QueryEvents.before_compile_delete` which complement
    :meth:`.QueryEvents.before_compile` in the case of the :meth:`.Query.update`
    and :meth:`.Query.delete` methods.


 .. change::
    :tags: bug, postgresql
    :tickets: 4463

    Revised the query used when reflecting CHECK constraints to make use of the
    ``pg_get_constraintdef`` function, as the ``consrc`` column is being
    deprecated in PG 12.  Thanks to John A Stevenson for the tip.


 .. change::
    :tags: bug, orm
    :tickets: 4454

    Fixed issue where when using single-table inheritance in conjunction with a
    joined inheritance hierarchy that uses &quot;with polymorphic&quot; loading, the
    &quot;single table criteria&quot; for that single-table entity could get confused for
    that of other entities from the same hierarchy used in the same query.The
    adaption of the &quot;single table criteria&quot; is made more specific to the target
    entity to avoid it accidentally getting adapted to other tables in the
    query.


 .. change::
    :tags: bug, oracle
    :tickets: 4457

    Fixed regression in integer precision logic due to the refactor of the
    cx_Oracle dialect in 1.2.  We now no longer apply the cx_Oracle.NATIVE_INT
    type to result columns sending integer values (detected as positive
    precision with scale ==0) which encounters integer overflow issues with
    values that go beyond the 32 bit boundary.  Instead, the output variable
    is left untyped so that cx_Oracle can choose the best option.

.. changelog::

Links

PyPI: https://pypi.org/project/sqlalchemy
Changelog: https://pyup.io/changelogs/sqlalchemy/
Homepage: http://www.sqlalchemy.org

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/jeffknupp/sandman2/pull/81 **Author:** [@pyup-bot](https://github.com/pyup-bot) **Created:** 1/28/2019 **Status:** ✅ Merged **Merged:** 1/28/2019 **Merged by:** [@jeffknupp](https://github.com/jeffknupp) **Base:** `master` ← **Head:** `pyup-scheduled-update-2019-01-28` --- ### 📝 Commits (1) - [`8e720a6`](https://github.com/jeffknupp/sandman2/commit/8e720a637c6fc4ac4ae4bee71396346dc2134e5e) Update sqlalchemy from 1.2.16 to 1.2.17 ### 📊 Changes **1 file changed** (+1 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `requirements.txt` (+1 -1) </details> ### 📄 Description ### Update [SQLAlchemy](https://pypi.org/project/SQLAlchemy) from **1.2.16** to **1.2.17**. <details> <summary>Changelog</summary> ### 1.2.17 ``` :released: January 25, 2019 .. change:: :tags: feature, orm :tickets: 4461 Added new event hooks :meth:`.QueryEvents.before_compile_update` and :meth:`.QueryEvents.before_compile_delete` which complement :meth:`.QueryEvents.before_compile` in the case of the :meth:`.Query.update` and :meth:`.Query.delete` methods. .. change:: :tags: bug, postgresql :tickets: 4463 Revised the query used when reflecting CHECK constraints to make use of the ``pg_get_constraintdef`` function, as the ``consrc`` column is being deprecated in PG 12. Thanks to John A Stevenson for the tip. .. change:: :tags: bug, orm :tickets: 4454 Fixed issue where when using single-table inheritance in conjunction with a joined inheritance hierarchy that uses "with polymorphic" loading, the "single table criteria" for that single-table entity could get confused for that of other entities from the same hierarchy used in the same query.The adaption of the "single table criteria" is made more specific to the target entity to avoid it accidentally getting adapted to other tables in the query. .. change:: :tags: bug, oracle :tickets: 4457 Fixed regression in integer precision logic due to the refactor of the cx_Oracle dialect in 1.2. We now no longer apply the cx_Oracle.NATIVE_INT type to result columns sending integer values (detected as positive precision with scale ==0) which encounters integer overflow issues with values that go beyond the 32 bit boundary. Instead, the output variable is left untyped so that cx_Oracle can choose the best option. .. changelog:: ``` </details> <details> <summary>Links</summary> - PyPI: https://pypi.org/project/sqlalchemy - Changelog: https://pyup.io/changelogs/sqlalchemy/ - Homepage: http://www.sqlalchemy.org </details> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>