From: mike bayer <mike_mp@zzzcomputing.com>
Date: Fri, 2 Sep 2016 16:23:31 +0000 (-0400)
Subject: Merge "Allow stringify compiler to render unnamed column"
X-Git-Tag: rel_1_1_0~36
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=ce62fa2eed1d93c9b6e383e48dcfaf5380b86915;p=thirdparty%2Fsqlalchemy%2Fsqlalchemy.git

Merge "Allow stringify compiler to render unnamed column"
---

ce62fa2eed1d93c9b6e383e48dcfaf5380b86915
diff --cc doc/build/changelog/changelog_11.rst
index 669f081884,c038966c5d..a097034891
--- a/doc/build/changelog/changelog_11.rst
+++ b/doc/build/changelog/changelog_11.rst
@@@ -21,21 -21,15 +21,30 @@@
  .. changelog::
      :version: 1.1.0
  
 +    .. change::
 +        :tags: bug, orm
 +        :tickets: 3788
 +
 +        Fixed bug where the "simple many-to-one" condition that allows  lazy
 +        loading to use get() from identity map would fail to be  invoked if the
 +        primaryjoin of the relationship had multiple clauses separated by AND
 +        which were not in the same order as that of the primary key columns
 +        being compared in each clause. This ordering
 +        difference occurs for a composite foreign key where the table-bound
 +        columns on the referencing side were not in the same order in the .c
 +        collection as the primary key columns on the referenced side....which
 +        in turn occurs a lot if one is using declarative mixins and/or
 +        declared_attr to set up columns.
 +
+     .. change::
+         :tags: bug, sql
+         :tickets: 3789
+ 
+         Stringify of expression with unnamed :class:`.Column` objects, as
+         occurs in lots of situations including ORM error reporting,
+         will now render the name in string context as "<name unknown>"
+         rather than raising a compile error.
+ 
      .. change::
          :tags: bug, sql
          :tickets: 3786