can have many B as children.
Thank you very much Michael !!
Best Regards,
Jeronimo
On Aug 15, 5:47 pm, Michael Bayer <[EMAIL PROTECTED]> wrote:
> hi Jeronimo -
>
> eager loading of self-referential relationships is not supported in
> version 0.3. this is a new fea
Greetengs !!
I'm having trouble getting a list from a recursive relationship. The
relation is between NodeA and NodeB, where NodeA whould be the parent
and NodeB the child.
If the recursive relatioship is lazy the list is loaded correctly when
the property is requested, but when child elements nee
Excelent ! It works perfectly !!
Thank you very much Michael. I was going crazy trying to figure how to
move
subquery to the from clause.
On Aug 9, 8:06 pm, Michael Bayer <[EMAIL PROTECTED]> wrote:
> OK sorry, i didn't look carefully enough. when you use a scalar
> subquery, you shouldn't acce
I cant manage to make sub_select appear at WHERE level, it always
appears at FROM level.
The SQL statement needs to select one node for each type, and each
node must be the one
with the max id in that type.
Is it possible to make this statement using SQLAlchemy ?
On Aug 9, 6:11 pm, Jeronimo
e_id)).as_scalar().correlate(n1)
> n1.select(n1.c.id==sub_query.c.max_id).execute().fetchall()
>
> however.it *should* be correlating automatically anyway...some
> combination of the "alias" and the no "scalar" might be affecting
> that in the 0.3 version...what vers
, 1, 1)]
It seems that sub_query is not using the parent query field
definitions, and instead is redeclaring node_table.
Does someone knows whats happening ? Thanks in advance !
Regards !
Jeronimo
--~--~-~--~~~---~--~~
You received this message because you are subs
, 1, 1)]
It seems that sub_query is not using the parent query field
definitions, and instead is redeclaring node_table.
Does someone knows whats happening ? Thanks in advance !
Regards !
Jeronimo
--~--~-~--~~~---~--~~
You received this message because you are subs
