github sqlalchemy/sqlalchemy rel_1_2_5


Released: March 6, 2018

  • [bug] [mysql] MySQL dialects now query the server version using SELECT @@version
    explicitly to the server to ensure we are getting the correct version
    information back. Proxy servers like MaxScale interfere with the value
    that is passed to the DBAPI's connection.server_version value so this
    is no longer reliable.

    This change is also backported to: 1.1.18

    References: #4205

  • [bug] [postgresql] [py3k] Fixed bug in PostgreSQL COLLATE / ARRAY adjustment first introduced
    in #4006 where new behaviors in Python 3.7 regular expressions
    caused the fix to fail.

    This change is also backported to: 1.1.18

    References: #4208

  • [bug] [sql] Fixed bug in :class:.CTE construct along the same lines as that of
    #4204 where a CTE that was aliased would not copy itself
    correctly during a "clone" operation as is frequent within the ORM as well
    as when using the ClauseElement.params() method.

    References: #4210

  • [bug] [orm] Fixed bug in new "polymorphic selectin" loading when a selection of
    polymorphic objects were to be partially loaded from a relationship
    lazy loader, leading to an "empty IN" condition within the load that
    raises an error for the "inline" form of "IN".

    References: #4199

  • [bug] [sql] Fixed bug in CTE rendering where a CTE that was also turned into
    an Alias would not render its "ctename AS aliasname" clause
    appropriately if there were more than one reference to the CTE in a FROM

    References: #4204

  • [bug] [orm] Fixed 1.2 regression where a mapper option that contains an
    AliasedClass object, as is typical when using the
    QueryableAttribute.of_type() method, could not be pickled. 1.1's
    behavior was to omit the aliased class objects from the path, so this
    behavior is restored.

    References: #4209

  • [feature] [orm] Added new feature Query.only_return_tuples(). Causes the
    Query object to return keyed tuple objects unconditionally even
    if the query is against a single entity. Pull request courtesy Eric

  • [bug] [sql] Fixed bug in new "expanding IN parameter" feature where the bind parameter
    processors for values wasn't working at all, tests failed to cover this
    pretty basic case which includes that ENUM values weren't working.

    References: #4198

latest releases: rel_1_3_20, rel_1_3_19, rel_1_3_18...
14 months ago