ahha !
every time i let the little inoccuous ones go through this is what we
get.
this is actually somewhat of a legacy behavior, as the idea of saying
class Foo(object):someattribute=list was the old way to specify the
"collection_class" setting, and thats whats happening here; attribute
instrumentation is mistaking the query options() method for a
collection class.
so, i want to take that old way out although im not sure if i should
do that before a major version release. so heres the workaround:
assign_mapper(CTX, OfferOption, offer_option, properties={
'offer': relation(OfferResponse, backref=backref('options',
collection_class=list))
})
On Jan 24, 2007, at 2:19 PM, JP wrote:
>
> (repeating my last ticket comment)
>
> Ok, I think I've tracked this down. The error is occurring because the
> name of the backref is 'options', which as of r2205 is being
> overwritten by assign_mapper.
>
> I'm not sure what's the right thing to do here. I don't think
> assign_mapper can avoid stepping on backrefs like this one, since (I
> think) the backref doesn't exist when assign_mapper is monkeypatching
> the domain model class.
>
> JP
>
>
> >
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
