On Oct 24, 2007, at 4:16 PM, Barry Hart wrote:
This subject came up on the TurboGears list and someone suggested I
post here.
I noticed a while back that in SqlAlchemy 0.3.x, if you have two
mapped classes A and B, and you define the same relationship (with
a backref) on both
- Original Message
From: Michael Bayer [EMAIL PROTECTED]
To: sqlalchemy@googlegroups.com
Sent: Wednesday, October 24, 2007 4:41:46 PM
Subject: [sqlalchemy] Re: Declaring a relationship twice - could SqlAlchemy
auto-detect problems like this?
On Oct 24, 2007, at 4:16 PM, Barry Hart wrote
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:
ok barry, the fix for this will be in 0.4.xx and will require some
tinkering, since backrefs when they configure do expect to find names
in both directions,
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
: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
