That is awesome -- thanks. I would've reported it sooner, but I thought maybe I was the only one silly enough to make these mistakes in my mappers. :-)
Barry ----- Original Message ---- From: Michael Bayer <[EMAIL PROTECTED]> To: sqlalchemy@googlegroups.com Sent: Wednesday, October 24, 2007 7:26:39 PM Subject: [sqlalchemy] Re: Declaring a relationship twice - could SqlAlchemy auto-detect problems like this? On Oct 24, 2007, at 5:02 PM, Barry Hart wrote: Here's what I had in mind. This set of mappings compiles without errors in 0.3.11: from sqlalchemy import * OK, thanks very much for pointing this one out, as it came across a big heap of egregious cruft in the backref code which I graciously flattened (it even included the phrase "if not x is not None"...so embarrassing...). It also raised a few surprises as there were a very small number of unit tests that were actually defining conflicting properties in this manner...so when people upgrade to 0.4.1 some people might get a few surprises (that alone makes it more controversial of a candidate for the 0.3 series, which is in "maintenance" mode). changeset is rev 3660. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
