Re: [Sqlalchemy-tickets] [sqlalchemy] #2948: clarify behavior of explicit primaryjoin wrt backref, including importance of establishing both sides for unusual cases

[sqlalchemy <mi...@zz...>]

#2948: clarify behavior of explicit primaryjoin wrt backref, including importance
of establishing both sides for unusual cases
--------------------------------+----------------------------------
      Reporter:  mkadin         |      Owner:  zzzeek
          Type:  defect         |     Status:  new
      Priority:  medium         |  Milestone:  0.9.xx
     Component:  documentation  |   Severity:  minor - half an hour
    Resolution:                 |   Keywords:
Progress State:  in queue       |
--------------------------------+----------------------------------

Comment (by mkadin):

 That makes sense.  I almost wonder if C might be the better choice?  If
 someone is asking sqlalchemy to do something it isn't sure about how to
 do, why not raise an error telling people to use a different primaryjoin?

--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2948#comment:2>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python