I wrote:
> Michael Bayer wrote:
>> thanks for the info. this should be the last of the compilation
>> bugs, fixed in rev 1686 .
>>
>
> Sorry, but 1686 breaks all my tests, failing at:
>
> File "/home/robert/tools/python/sqlalchemy/lib/sqlalchemy/orm/mapper.py",
> line
> 196, in compile
>
Michael Bayer wrote:
>
> thanks for the info. this should be the last of the compilation
> bugs, fixed in rev 1686 .
>
Sorry, but 1686 breaks all my tests, failing at:
File "/home/robert/tools/python/sqlalchemy/lib/sqlalchemy/orm/mapper.py", line
196, in compile
assert len(_compile_tri
Updating to 1686 did fix the problem. Thanks.
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.n
steve -
thanks for the info. this should be the last of the compilation
bugs, fixed in rev 1686 .
- mike
On Jul 5, 2006, at 4:02 PM, Steve Zatz wrote:
>> so let me see what your mapper setup looks like.
>
> mapper(Item, item_table, properties = dict(keywords =
> relation(Keyword, secondary=i
I cant reproduce this behavior: the Reminder mapper definitely has
an 'item' property on it as you describe, and also if it didnt, thats
not the error message you would get for that line.
can you please submit a fully working test case ?
On Jul 4, 2006, at 11:06 PM, Steve Zatz wrote:
> It
It seems that if you define a mapper relationship through a backref,
that relationship does not appear to be 'visible' when setting options
on a query.
For example:
mapper(Item, item_table, properties = {'reminder': relation(Reminder,
backref='item')})
mapper(Reminder, reminder_table)
If you th
6 matches
Mail list logo
