On Sunday, June 9, 2013 5:38:36 PM UTC-7, Michael Bayer wrote: > > > On Jun 9, 2013, at 8:06 PM, Michael Bayer > <mik...@zzzcomputing.com<javascript:>> > wrote: > > > > > SELECT items.id AS items_id, items.item_type AS items_item_type, > items.parent_id AS items_parent_id, items_ext.id AS items_ext_id, > items_ext.custom_name AS items_ext_custom_name, items_1.id AS items_1_id, > items_1.item_type AS items_1_item_type, items_1.parent_id AS > items_1_parent_id, items_ext_1.id AS items_ext_1_id, > items_ext_1.custom_name AS items_ext_1_custom_name > > FROM items LEFT OUTER JOIN items_ext ON items.id = items_ext.id LEFT > OUTER JOIN (items AS items_1 LEFT OUTER JOIN items_ext AS items_ext_1 ON > items_1.id = items_ext_1.id) ON items.id = items_1.parent_id > > > > please let me know if MySQL is still impacted by the parenthesis, x LEFT > OUTER JOIN (y LEFT OUTER JOIN z). If the string of joins have all the same > "outerness", they can be flattened out at compile time as well with a join > rewriting scheme. > > I just tested on 0.9dev and it seems to be working perfectly. The 'single select' query that was generated looked perfect when I EXPLAINED it (all using const) , so I think you may have just fixed my biggest (only?) gripe with sqlalchemy. :D Thanks a ton for this one Michael, those subqueries have been killing me. This is fantastic!
-- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to sqlalchemy+unsubscr...@googlegroups.com. To post to this group, send email to sqlalchemy@googlegroups.com. Visit this group at http://groups.google.com/group/sqlalchemy?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
