Thanks. I have it working in SQL expression language, using text in execute(). For better modularity and scalabililty, I will probably move it over to using the select(), join(), etc. functions that are built in.
On Nov 7, 5:26 pm, "Rick Morrison" <[EMAIL PROTECTED]> wrote: > One of the reasons that Query.select() is deprecated is that the way it was > named led to this kind of confusion. > > The Query() class is used for ORM operations, and when it's used as mapped > against a table, it's going to give you all the columns from the table by > default. There are ways of defining the table mapper to only get one column, > but I suspect that you are really barking up the wrong tree, and want to use > the non-ORM or "SQL expression" part of SqlAlchemy. > > It's that library that Barry was referring to. > Using that library, it's going to be really easy to specify only the > columns that you want, and apply things like DISTINCT. > Read the docs on SQL expressions and try what he's suggesting. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
