Re: When I select a single column, can I prevent getting a list of one-element tuples? - Mailing list psycopg

From W. Matthew Wilson
Subject Re: When I select a single column, can I prevent getting a list of one-element tuples?
Date
Msg-id CAGHfCUD0HqFmAWieaBqy+Ajj=r9BKGtGtZYAbrLyNZCdTAgkxg@mail.gmail.com
Whole thread Raw
In response to Re: When I select a single column, can I prevent getting a list of one-element tuples?  (Daniele Varrazzo <daniele.varrazzo@gmail.com>)
Responses Re: When I select a single column, can I prevent getting a list of one-element tuples?
List 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 by date:

Previous
From: Nicolas Grilly
Date:
Subject: Re: connection pooling in web apps
Next
From: Nick Cash
Date:
Subject: Re: When I select a single column, can I prevent getting a list of one-element tuples?