{"action":"created","issue":{"url":"https://api.github.com/repos/GuangTianLi/restalchemy/issues/19","repository_url":"https://api.github.com/repos/GuangTianLi/restalchemy","labels_url":"https://api.github.com/repos/GuangTianLi/restalchemy/issues/19/labels{/name}","comments_url":"https://api.github.com/repos/GuangTianLi/restalchemy/issues/19/comments","events_url":"https://api.github.com/repos/GuangTianLi/restalchemy/issues/19/events","html_url":"https://github.com/GuangTianLi/restalchemy/pull/19","id":379466057,"node_id":"MDExOlB1bGxSZXF1ZXN0MjI5OTE2Mjc2","number":19,"title":"Update sqlalchemy to 1.2.14","user":{"login":"pyup-bot","id":16239342,"node_id":"MDQ6VXNlcjE2MjM5MzQy","avatar_url":"https://avatars0.githubusercontent.com/u/16239342?v=4","gravatar_id":"","url":"https://api.github.com/users/pyup-bot","html_url":"https://github.com/pyup-bot","followers_url":"https://api.github.com/users/pyup-bot/followers","following_url":"https://api.github.com/users/pyup-bot/following{/other_user}","gists_url":"https://api.github.com/users/pyup-bot/gists{/gist_id}","starred_url":"https://api.github.com/users/pyup-bot/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/pyup-bot/subscriptions","organizations_url":"https://api.github.com/users/pyup-bot/orgs","repos_url":"https://api.github.com/users/pyup-bot/repos","events_url":"https://api.github.com/users/pyup-bot/events{/privacy}","received_events_url":"https://api.github.com/users/pyup-bot/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-11-10T22:04:38Z","updated_at":"2018-12-11T23:05:44Z","closed_at":null,"author_association":"CONTRIBUTOR","pull_request":{"url":"https://api.github.com/repos/GuangTianLi/restalchemy/pulls/19","html_url":"https://github.com/GuangTianLi/restalchemy/pull/19","diff_url":"https://github.com/GuangTianLi/restalchemy/pull/19.diff","patch_url":"https://github.com/GuangTianLi/restalchemy/pull/19.patch"},"body":"\nThis PR updates [sqlalchemy](https://pypi.org/project/sqlalchemy) from **1.2.11** to **1.2.14**.\n\n\n\n<details>\n  <summary>Changelog</summary>\n  \n  \n   ### 1.2.14\n   ```\n   :released: November 10, 2018\n\n    .. change::\n       :tags: bug, orm\n       :tickets: 4357\n\n       Fixed bug in :meth:`.Session.bulk_update_mappings` where alternate mapped\n       attribute names would result in the primary key column of the UPDATE\n       statement being included in the SET clause, as well as the WHERE clause;\n       while usually harmless, for SQL Server this can raise an error due to the\n       IDENTITY column.  This is a continuation of the same bug that was fixed in\n       :ticket:`3849`, where testing was insufficient to catch this additional\n       flaw.\n\n    .. change::\n        :tags: bug, mysql\n        :tickets: 4361\n\n        Fixed regression caused by :ticket:`4344` released in 1.2.13, where the fix\n        for MySQL 8.0&#39;s case sensitivity problem with referenced column names when\n        reflecting foreign key referents is worked around using the\n        ``information_schema.columns`` view.  The workaround was failing on OSX /\n        ``lower_case_table_names=2`` which produces non-matching casing for the\n        ``information_schema.columns`` vs. that of ``SHOW CREATE TABLE``, so in\n        case-insensitive SQL modes case-insensitive matching is now used.\n\n    .. change::\n       :tags: bug, orm\n       :tickets: 4347\n\n       Fixed a minor performance issue which could in some cases add unnecessary\n       overhead to result fetching, involving the use of ORM columns and entities\n       that include those same columns at the same time within a query.  The issue\n       has to do with hash / eq overhead when referring to the column in different\n       ways.\n\n.. changelog::\n   ```\n   \n  \n  \n   ### 1.2.13\n   ```\n   :released: October 31, 2018\n\n    .. change::\n       :tags: bug, postgresql\n       :tickets: 4337\n\n       Added support for the :class:`.aggregate_order_by` function to receive\n       multiple ORDER BY elements, previously only a single element was accepted.\n\n\n    .. change::\n       :tags: bug, mysql\n       :tickets: 4348\n\n       Added word ``function`` to the list of reserved words for MySQL, which is\n       now a keyword in MySQL 8.0\n\n    .. change::\n        :tags: feature, sql\n        :versions: 1.3.0b1\n\n        Refactored :class:`.SQLCompiler` to expose a\n        :meth:`.SQLCompiler.group_by_clause` method similar to the\n        :meth:`.SQLCompiler.order_by_clause` and :meth:`.SQLCompiler.limit_clause`\n        methods, which can be overridden by dialects to customize how GROUP BY\n        renders.  Pull request courtesy Samuel Chou.\n\n    .. change::\n       :tags: bug, misc\n\n       Fixed issue where part of the utility language helper internals was passing\n       the wrong kind of argument to the Python ``__import__`` builtin as the list\n       of modules to be imported.  The issue produced no symptoms within the core\n       library but could cause issues with external applications that redefine the\n       ``__import__`` builtin or otherwise instrument it. Pull request courtesy Joe\n       Urciuoli.\n\n    .. change::\n       :tags: bug, orm\n       :tickets: 4349\n\n       Fixed bug where &quot;dynamic&quot; loader needs to explicitly set the &quot;secondary&quot;\n       table in the FROM clause of the query, to suit the case where the secondary\n       is a join object that is otherwise not pulled into the query from its\n       columns alone.\n\n\n    .. change::\n       :tags: bug, orm, declarative\n       :tickets: 4350\n\n       Fixed regression caused by :ticket:`4326` in version 1.2.12 where using\n       :class:`.declared_attr` with a mixin in conjunction with\n       :func:`.orm.synonym` would fail to map the synonym properly to an inherited\n       subclass.\n\n    .. change::\n       :tags: bug, misc, py3k\n       :tickets: 4339\n\n       Fixed additional warnings generated by Python 3.7 due to changes in the\n       organization of the Python ``collections`` and ``collections.abc`` packages.\n       Previous ``collections`` warnings were fixed in version 1.2.11. Pull request\n       courtesy xtreak.\n\n    .. change::\n       :tags: bug, ext\n\n       Added missing ``.index()`` method to list-based association collections\n       in the association proxy extension.\n\n    .. change::\n       :tags: bug, mysql\n       :tickets: 4344\n\n       Added a workaround for a MySQL bug 88718 introduced in the 8.0 series,\n       where the reflection of a foreign key constraint is not reporting the\n       correct case sensitivity for the referred column, leading to errors during\n       use of the reflected constraint such as when using the automap extension.\n       The workaround emits an additional query to the information_schema tables in\n       order to retrieve the correct case sensitive name.\n\n    .. change::\n       :tags: bug, sql\n       :tickets: 4341\n\n       Fixed bug where the :paramref:`.Enum.create_constraint` flag on  the\n       :class:`.Enum` datatype would not be propagated to copies of the type, which\n       affects use cases such as declarative mixins and abstract bases.\n\n    .. change::\n       :tags: bug, orm, declarative\n       :tickets: 4352\n\n       The column conflict resolution technique discussed at\n       :ref:`declarative_column_conflicts` is now functional for a :class:`.Column`\n       that is also a primary key column.  Previously, a check for primary key\n       columns declared on a single-inheritance subclass would occur before the\n       column copy were allowed to pass.\n\n\n.. changelog::\n   ```\n   \n  \n  \n   ### 1.2.12\n   ```\n   :released: September 19, 2018\n\n    .. change::\n        :tags: bug, postgresql\n        :tickets: 4325\n\n        Fixed bug in PostgreSQL dialect where compiler keyword arguments such as\n        ``literal_binds=True`` were not being propagated to a DISTINCT ON\n        expression.\n\n    .. change::\n        :tags: bug, ext\n        :tickets: 4328\n\n        Fixed issue where :class:`.BakedQuery` did not include the specific query\n        class used by the :class:`.Session` as part of the cache key, leading to\n        incompatibilities when using custom query classes, in particular the\n        :class:`.ShardedQuery` which has some different argument signatures.\n\n    .. change::\n        :tags: bug, postgresql\n        :tickets: 4324\n\n        Fixed the :func:`.postgresql.array_agg` function, which is a slightly\n        altered version of the usual :func:`.functions.array_agg` function, to also\n        accept an incoming &quot;type&quot; argument without forcing an ARRAY around it,\n        essentially the same thing that was fixed for the generic function in 1.1\n        in :ticket:`4107`.\n\n    .. change::\n        :tags: bug, postgresql\n        :tickets: 4323\n\n        Fixed bug in PostgreSQL ENUM reflection where a case-sensitive, quoted name\n        would be reported by the query including quotes, which would not match a\n        target column during table reflection as the quotes needed to be stripped\n        off.\n\n\n    .. change::\n       :tags: bug, orm\n\n       Added a check within the weakref cleanup for the :class:`.InstanceState`\n       object to check for the presence of the ``dict`` builtin, in an effort to\n       reduce error messages generated when these cleanups occur during interpreter\n       shutdown.  Pull request courtesy Romuald Brunet.\n\n    .. change::\n        :tags: bug, orm, declarative\n        :tickets: 4326\n\n        Fixed bug where the declarative scan for attributes would receive the\n        expression proxy delivered by a hybrid attribute at the class level, and\n        not the hybrid attribute itself, when receiving the descriptor via the\n        ``declared_attr`` callable on a subclass of an already-mapped class. This\n        would lead to an attribute that did not report itself as a hybrid when\n        viewed within :attr:`.Mapper.all_orm_descriptors`.\n\n\n    .. change::\n        :tags: bug, orm\n        :tickets: 4334\n        :versions: 1.3.0b1\n\n        Fixed bug where use of :class:`.Lateral` construct in conjunction with\n        :meth:`.Query.join` as well as :meth:`.Query.select_entity_from` would not\n        apply clause adaption to the right side of the join.   &quot;lateral&quot; introduces\n        the use case of the right side of a join being correlatable.  Previously,\n        adaptation of this clause wasn&#39;t considered.   Note that in 1.2 only,\n        a selectable introduced by :meth:`.Query.subquery` is still not adapted\n        due to :ticket:`4304`; the selectable needs to be produced by the\n        :func:`.select` function to be the right side of the &quot;lateral&quot; join.\n\n    .. change::\n       :tags: bug, oracle\n       :tickets: 4335\n\n       Fixed issue for cx_Oracle 7.0 where the behavior of Oracle param.getvalue()\n       now returns a list, rather than a single scalar value, breaking\n       autoincrement logic throughout the Core and ORM. The dml_ret_array_val\n       compatibility flag is used for cx_Oracle 6.3 and 6.4 to establish compatible\n       behavior with 7.0 and forward, for cx_Oracle 6.2.1 and prior a version\n       number check falls back to the old logic.\n\n\n    .. change::\n        :tags: bug, orm\n        :tickets: 4327\n\n        Fixed 1.2 regression caused by :ticket:`3472` where the handling of an\n        &quot;updated_at&quot; style column within the context of a post-update operation\n        would also occur for a row that is to be deleted following the update,\n        meaning both that a column with a Python-side value generator would show\n        the now-deleted value that was emitted for the UPDATE before the DELETE\n        (which was not the previous behavor), as well as that a SQL- emitted value\n        generator would have the attribute expired, meaning the previous value\n        would be unreachable due to the row having been deleted and the object\n        detached from the session.The &quot;postfetch&quot; logic that was added as part of\n        :ticket:`3472` is now skipped entirely for an object that ultimately is to\n        be deleted.\n\n.. changelog::\n   ```\n   \n  \n</details>\n\n\n \n\n<details>\n  <summary>Links</summary>\n  \n  - PyPI: https://pypi.org/project/sqlalchemy\n  - Changelog: https://pyup.io/changelogs/sqlalchemy/\n  - Homepage: http://www.sqlalchemy.org\n</details>\n\n"},"comment":{"url":"https://api.github.com/repos/GuangTianLi/restalchemy/issues/comments/446396929","html_url":"https://github.com/GuangTianLi/restalchemy/pull/19#issuecomment-446396929","issue_url":"https://api.github.com/repos/GuangTianLi/restalchemy/issues/19","id":446396929,"node_id":"MDEyOklzc3VlQ29tbWVudDQ0NjM5NjkyOQ==","user":{"login":"pyup-bot","id":16239342,"node_id":"MDQ6VXNlcjE2MjM5MzQy","avatar_url":"https://avatars0.githubusercontent.com/u/16239342?v=4","gravatar_id":"","url":"https://api.github.com/users/pyup-bot","html_url":"https://github.com/pyup-bot","followers_url":"https://api.github.com/users/pyup-bot/followers","following_url":"https://api.github.com/users/pyup-bot/following{/other_user}","gists_url":"https://api.github.com/users/pyup-bot/gists{/gist_id}","starred_url":"https://api.github.com/users/pyup-bot/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/pyup-bot/subscriptions","organizations_url":"https://api.github.com/users/pyup-bot/orgs","repos_url":"https://api.github.com/users/pyup-bot/repos","events_url":"https://api.github.com/users/pyup-bot/events{/privacy}","received_events_url":"https://api.github.com/users/pyup-bot/received_events","type":"User","site_admin":false},"created_at":"2018-12-11T23:05:44Z","updated_at":"2018-12-11T23:05:44Z","author_association":"CONTRIBUTOR","body":"Closing this in favor of #23"}}
{"actor":{"display_login":"pyup-bot"}}