> <snip> But now a user of the query > needs to know about the underlying selectable itself
In case anyone reads this for info, that last statement is not true because you can access the columns from the mapped class. See http://www.sqlalchemy.org/docs/datamapping.html#datamapping_query_columnsonclass. In fact, you can even get at the mapped columns, and presumably synonyms, via query_instance.mapper.c. So if someone really did want to wrap a SA Query to look, act and walk a little bit like Django's Model.objects (just to be constitent!) it would be pretty straightforward. Thanks, 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 -~----------~----~----~----~------~----~------~--~---
