Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update sqlalchemy to 1.2.2 #2837

Merged
merged 2 commits into from
Jan 26, 2018
Merged

Conversation

pyup-bot
Copy link
Contributor

There's a new version of sqlalchemy available.
You are currently using 1.2.1. I have updated it to 1.2.2

These links might come in handy: PyPI | Changelog | Homepage

Changelog

1.2.2

:released: January 24, 2018

.. change::
:tags: bug, mssql
🎟️ 4164

   Added ODBC error code 10054 to the list of error
   codes that count as a disconnect for ODBC / MSSQL server.

.. change::
:tags: bug, orm
🎟️ 4171

   Fixed 1.2 regression regarding new bulk_replace event
   where a backref would fail to remove an object from the
   previous owner when a bulk-assignment assigned the
   object to a new owner.

.. change::
:tags: bug, oracle
🎟️ 4163

   The cx_Oracle dialect now calls setinputsizes() with cx_Oracle.NCHAR
   unconditionally when the NVARCHAR2 datatype, in SQLAlchemy corresponding
   to sqltypes.Unicode(), is in use.  Per cx_Oracle's author this allows
   the correct conversions to occur within the Oracle client regardless
   of the setting for NLS_NCHAR_CHARACTERSET.

.. change::
:tags: bug, mysql

   Added more MySQL 8.0 reserved words to the MySQL dialect
   for quoting purposes.  Pull request courtesy
   Riccardo Magliocchetti.

.. changelog::

Got merge conflicts? Close this PR and delete the branch. I'll create a new PR for you.

Happy merging! 🤖

@alex alex merged commit d61cf86 into master Jan 26, 2018
@alex alex deleted the pyup-update-sqlalchemy-1.2.1-to-1.2.2 branch January 26, 2018 15:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants