On Jan 18, 2010, at 3:35 PM, PauloS wrote:

> On Jan 16, 4:06 pm, Michael Bayer <mike...@zzzcomputing.com> wrote:
>> OK SQLSoup is using the Session.extension which adds a ".query" attribute 
>> unconditionally.   this bug is fixed in trunk.   I can't do it in 0.5 since 
>> .query is a public API that people might be relying upon.   To work around 
>> in 0.5 do:
>> 
>> sqlsoup = SqlSoup(engine)
>> my_table = Table("my_table", Column("query", String, key="query_col"), 
>> autoload=True, autoload_with=engine)
>> MyClass = sqlsoup.map(my_table)
>> 
>> # use MyClass.query_col
>> 
> 
> Thanks.
> 
> How was that fixed in trunk, the atribute was renamed to _query or
> something like that?

it was actually always there as _query for internal use.     the "query" was 
coming from the usage of Session.mapper, which it no longer uses.




> 
> Regards,
> --
> Paulo
> -- 
> You received this message because you are subscribed to the Google Groups 
> "sqlalchemy" group.
> To post to this group, send email to sqlalch...@googlegroups.com.
> To unsubscribe from this group, send email to 
> sqlalchemy+unsubscr...@googlegroups.com.
> For more options, visit this group at 
> http://groups.google.com/group/sqlalchemy?hl=en.
> 
> 

-- 
You received this message because you are subscribed to the Google Groups 
"sqlalchemy" group.
To post to this group, send email to sqlalch...@googlegroups.com.
To unsubscribe from this group, send email to 
sqlalchemy+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/sqlalchemy?hl=en.


Reply via email to