Re: [sqlalchemy] problem with select([table.c.column1, table.c.column1])

2010-06-22 Thread Michael Bayer
On Jun 21, 2010, at 7:52 PM, Jon Nelson wrote: On Mon, Jun 21, 2010 at 5:55 PM, Michael Bayer mike...@zzzcomputing.com wrote: not a bug, that's the correct behavior. Can you explain how it is correct? I asked for two things but I only got one. Why should it matter if they happen to be

Re: [sqlalchemy] problem with select([table.c.column1, table.c.column1])

2010-06-22 Thread Jon Nelson
On Tue, Jun 22, 2010 at 8:55 AM, Michael Bayer mike...@zzzcomputing.com wrote: On Jun 21, 2010, at 7:52 PM, Jon Nelson wrote: On Mon, Jun 21, 2010 at 5:55 PM, Michael Bayer mike...@zzzcomputing.com wrote: not a bug, that's the correct behavior. Can you explain how it is correct? I asked

[sqlalchemy] problem with select([table.c.column1, table.c.column1])

2010-06-21 Thread Jon Nelson
I'm encountering a problem with SA 0.6.1 I have a select statement which selects the same column twice (and some other stuff, too). However, when the query is run (or printed), the column only shows up once. This seems like a bug. Example: from sqlalchemy import create_engine, select, Table,

Re: [sqlalchemy] problem with select([table.c.column1, table.c.column1])

2010-06-21 Thread Michael Bayer
not a bug, that's the correct behavior. On Jun 21, 2010, at 5:35 PM, Jon Nelson wrote: I'm encountering a problem with SA 0.6.1 I have a select statement which selects the same column twice (and some other stuff, too). However, when the query is run (or printed), the column only shows up

Re: [sqlalchemy] problem with select([table.c.column1, table.c.column1])

2010-06-21 Thread Jon Nelson
On Mon, Jun 21, 2010 at 5:55 PM, Michael Bayer mike...@zzzcomputing.com wrote: not a bug, that's the correct behavior. Can you explain how it is correct? I asked for two things but I only got one. Why should it matter if they happen to be the /same/ thing? In this particular case, I need it for