query(SomeJoinedTableClass).filter(SomeJoinedTableClass.foo.contains(bar)) generates quasi-invalid SQL

[Mike Bayer]

i.e. of the form:

select * from
bar_table, base_table JOIN subclass_table on base_table.id=subclass_table.id
WHERE base_table.id=bar_table.base_id AND bar_table.other_id=<bar id>

postgres accepts this but we've heard MySQL 5 does not. verify mysql blows up on this form.

not sure what solution there could be to this one since contains() is not going to make implications about the overall FROM clause that would allow the joined-table query to be aliased.

[Mike Bayer]

FWIW, if you have a m2m relationship to a joined table mapping, the lazy load of the target also produces "select * from secondary, target_base join target_child on <>". It works fine in MySQL 5 over here. So I'm becoming skeptical that there's any issue here.

[Mike Bayer]

Removing milestone: 0.6.xx (automated comment)