Re: When I select a single column, can I prevent getting a list of one-element tuples?
От | W. Matthew Wilson |
---|---|
Тема | Re: When I select a single column, can I prevent getting a list of one-element tuples? |
Дата | |
Msg-id | CAGHfCUD0HqFmAWieaBqy+Ajj=r9BKGtGtZYAbrLyNZCdTAgkxg@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: When I select a single column, can I prevent getting a list of one-element tuples? (Daniele Varrazzo <daniele.varrazzo@gmail.com>) |
Ответы |
Re: When I select a single column, can I prevent getting
a list of one-element tuples?
|
Список | psycopg |
On Sun, Jun 17, 2012 at 12:32 PM, Daniele Varrazzo <daniele.varrazzo@gmail.com> wrote: > No, there's nothing like this. For me, any attempt to add a feature > and let the user choose whether to return one-column queries just as > lists or as one-item tuples (a cursor subclass? a function?) seems > more verbose than the [r[0] for r in cur] or map(itemgetter(0), cur) > to get the data the way you want. Thanks for the reply! Mostly I wanted to make sure there wasn't already a standard solution out there. For me, it just feels goofy to write something like [row[0] for row in cursor.fetchall()], but I understand where you are coming from. I like the cursor subclass idea so maybe I'll take a shot at something like that. Matt -- W. Matthew Wilson matt@tplus1.com http://tplus1.com
В списке psycopg по дате отправления: