github sqlalchemy/sqlalchemy rel_1_2_15
1.2.15

latest releases: rel_2_0_29, rel_2_0_28, rel_1_4_52...
4 years ago

1.2.15

Released: December 11, 2018

  • [bug] [orm] Fixed bug where the ORM annotations could be incorrect for the
    primaryjoin/secondaryjoin a relationship if one used the pattern
    ForeignKey(SomeClass.id) in the declarative mappings. This pattern
    would leak undesired annotations into the join conditions which can break
    aliasing operations done within Query that are not supposed to
    impact elements in that join condition. These annotations are now removed
    up front if present.

    References: #4367

  • [bug] [declarative] [orm] A warning is emitted in the case that a column() object is applied to
    a declarative class, as it seems likely this intended to be a
    Column object.

    References: #4374

  • [bug] [orm] In continuing with a similar theme as that of very recent #4349,
    repaired issue with RelationshipProperty.Comparator.any() and
    RelationshipProperty.Comparator.has() where the "secondary"
    selectable needs to be explicitly part of the FROM clause in the
    EXISTS subquery to suit the case where this "secondary" is a Join
    object.

    References: #4366

  • [bug] [orm] Fixed regression caused by #4349 where adding the "secondary"
    table to the FROM clause for a dynamic loader would affect the ability of
    the Query to make a subsequent join to another entity. The fix
    adds the primary entity as the first element of the FROM list since
    Query.join() wants to jump from that. Version 1.3 will have
    a more comprehensive solution to this problem as well (#4365).

    References: #4363

  • [bug] [orm] Fixed bug where chaining of mapper options using
    RelationshipProperty.of_type() in conjunction with a chained option
    that refers to an attribute name by string only would fail to locate the
    attribute.

  • Added support for the write_timeout flag accepted by mysqlclient and
    pymysql to be passed in the URL string.

    References: #4381

  • Fixed issue where reflection of a PostgreSQL domain that is expressed as an
    array would fail to be recognized. Pull request courtesy Jakub Synowiec.

    References: #4377, #4380

Don't miss a new sqlalchemy release

NewReleases is sending notifications on new releases.