> django's method of shoving SQL operators into the names of keyword > arguments seems horribly ugly to me. SQLAlchemy's approach is to > use query.filter(sometable.c.col.in_(x, y)). it uses the same > operators as everything else without the need to memorize magic codes > to embed in keyword names. select_by() is deprecated in the > upcoming 0.4 series.
I appreciate the appeal to aesthetics. But now a user of the query needs to know about the underlying selectable itself and not just the field names. It seems to lessens the utility of the filter_by method. Anyhow, thanks for the help. SA is remarkable. Peace, David S. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
