On Friday 27 June 2008 22:09:39 Michael Bayer wrote: > On Jun 27, 2008, at 3:11 PM, [EMAIL PROTECTED] wrote: > > On Friday 27 June 2008 21:58:22 Michael Bayer wrote: > >> 0.4 has trouble joining *to* a joined-table mapper, as below you > >> can see its failing to convert "model join paramvalue" into a > >> subquery. what's 0.5 say ? > > > > seems to work, on the simplified case at least. > > how many times are you going to bang your head against this wall ? > :) (picking a screwdriver from pocket and.. beware,wall!) 0.5 - what's the equivalent of 0.4's someproperty.expression_element() i.e. how to get the clause-column of a (mapped) property? for both columnProp or PropLoader/*to1 or in 0.5 myclass.mycol is really a good substitute for mytable.c.mycol for any clause-expression?
btw a suggestion on that 0.5 subselect: the subselect for (A join B) is auto-aliased as anonxxx, but might be more useful to be aliased as B_xxx. i have 10 of those and it is very hard to see which anonxxx is actualy which B, C, D, or F. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
