Yep, it seems that this was just 0.4.0 getting confused about my
redundant relationships. It's working now.

Thanks for actually looking at my code.

On Nov 30, 4:36 pm, Jonathon Anderson <[EMAIL PROTECTED]> wrote:
> I just updated to sqlalchemy 0.4.1, and see the error. I'll remove the
> duplicate relations, and see if that clears this up.
>
> On Nov 30, 4:30 pm, Michael Bayer <[EMAIL PROTECTED]> wrote:
>
> > On Nov 30, 5:18 pm, Jonathon Anderson <[EMAIL PROTECTED]> wrote:
>
> > > I'm on SA 0.4.0
>
> > > I was under the impression that you had to declare the relationship
> > > from both sides, and that backref was only used to update related
> > > objects when one side of the relation was changed. Can you point me to
> > > some docs for this?
>
> > we have some tutorial docs 
> > athttp://www.sqlalchemy.org/docs/04/ormtutorial.html#datamapping_relati...
>
> > the most specific M2M example is in the mapper config 
> > docs:http://www.sqlalchemy.org/docs/04/mappers.html#advdatamapping_relatio...
>
> > and the generated docstrings for relation() also have some info on
> > it:  
> > http://www.sqlalchemy.org/docs/04/sqlalchemy_orm.html#docstrings_sqla...
>
> > but also, using 0.4.1 the config you had should raise an error which
> > is also a form of "documentation".
>
> > it probably wouldn't hurt to add a very explicit "Backreferences"
> > section to the "mapper" docs.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"sqlalchemy" group.
To post to this group, send email to sqlalchemy@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/sqlalchemy?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to