weird, my test case still works if I remove the 0.1.2 fix (but
tracing out i get the 994 calls again)
On Feb 24, 2006, at 12:13 PM, [EMAIL PROTECTED] wrote:
Yes I'm pretty sure. Upgraded sqlalchemy and suddenly it was unbroken.
Quoting Michael Bayer <[EMAIL PROTECTED]>:
nothing has cha
Yes I'm pretty sure. Upgraded sqlalchemy and suddenly it was unbroken.
Quoting Michael Bayer <[EMAIL PROTECTED]>:
> nothing has changed since 0.1.1 except for a recursive bug ? are you
> sure that youre observing different behavior between 0.1.1 and 0.1.2 ?
>
> On Feb 24, 2006, at 9:51 AM, [EMAIL
nothing has changed since 0.1.1 except for a recursive bug ? are you
sure that youre observing different behavior between 0.1.1 and 0.1.2 ?
i suspect we havent seen the last of this weird "_impl" issue. i
have plans to rework that whole relationship anyway.
On Feb 24, 2006, at 9:51 AM, [E
> AttributeError: 'ColumnImpl' object has no attribute 'references'
Ah, this seems to be resolved for both inheritance and nested joins in 0.1.2,
sorry.
---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extend
Hi,
I find that nested joins are broken as in:
join(join(foo, bar), blubber)
Where bar references foo and blubber references bar.
I get the error:
AttributeError: 'ColumnImpl' object has no attribute 'references'
Kind Regards,
Florian
---
Thi
5 matches
Mail list logo