i have a premade filtering clause and give it to a query.select at runtime. Sometimes its a simple x == 13 expression, another time it is a full sql-construct like polymorphic_union().
in 0.3 all went into .select(), but in 0.4 these 2 kinds seems split between .from_statement and .filter. so i have either to check at runtime which one to call, or make the simple expression into sql construct. why filter() does not accept everything as before? IMO the types are distinct enough to check/switch... or, let filter() be, why not have another single method that accepts everything? All that is a filter anyway --~--~---------~--~----~------------~-------~--~----~ 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 email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
