On Aug 26, 2008, at 8:24 AM, ml wrote:
>
>> thats a bug which was fixed post 0.4.7p1. Its in trunk and is for
>> 0.4.8.
>
> Great!
>
> And back to the mapper properties. As I found it always do a
> polymorphic_fetch=select-like query when dealing with mapper
> properties
> referencing a polym
> thats a bug which was fixed post 0.4.7p1. Its in trunk and is for
> 0.4.8.
Great!
And back to the mapper properties. As I found it always do a
polymorphic_fetch=select-like query when dealing with mapper properties
referencing a polymorphic base. This is not very efficient. I would
prefer an
sorry not trunk, the head of the 0.4 branch.
--~--~-~--~~~---~--~~
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
On Aug 25, 2008, at 5:38 PM, ml wrote:
> I created a stripped version of my application's model and I found the
> problem. The problem is not in the polymorphism but int the
> inheritance
> condition. I have cycles in my model so I had to use the
> inherit_condition. I found that it is a big d
I created a stripped version of my application's model and I found the
problem. The problem is not in the polymorphism but int the inheritance
condition. I have cycles in my model so I had to use the
inherit_condition. I found that it is a big difference how I choose the
expression sides
inherit_c
On Aug 25, 2008, at 1:05 PM, ml wrote:
>
> One more thing :-)
>
> Now I have polymorphic_fetch="deferred" and in some needed cases I
> call
> query.with_polymorphic("*"). All works perfectly. But can I setup
> something like with_polymorphic("*") on a mapper property? Because now
> all relatio
One more thing :-)
Now I have polymorphic_fetch="deferred" and in some needed cases I call
query.with_polymorphic("*"). All works perfectly. But can I setup
something like with_polymorphic("*") on a mapper property? Because now
all relations to Base are polymorphic-deferred and it does me some tr
