Re: RealDictCursor behavior question

From: Israel Brewster <ibrewster(at)flyravn(dot)com>
To: Christophe Pettus <xof(at)thebuild(dot)com>
Cc: Daniele Varrazzo <daniele(dot)varrazzo(at)gmail(dot)com>, "psycopg(at)postgresql(dot)org" <psycopg(at)postgresql(dot)org>
Subject: Re: RealDictCursor behavior question
Date: 2018-04-30 19:27:14
Message-ID: 7B6B823E-11F9-46C3-A7E4-8195867A099A@flyravn.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: psycopg

On Apr 30, 2018, at 11:24 AM, Christophe Pettus <xof(at)thebuild(dot)com<mailto:xof(at)thebuild(dot)com>> wrote:

On Apr 30, 2018, at 12:19, Israel Brewster <ibrewster(at)flyravn(dot)com<mailto:ibrewster(at)flyravn(dot)com>> wrote:
Yes, that is good reasoning *in general*, however in my particular use case, using `select *` makes things so much cleaner as to be worth the -again, in my use case - quite small risk. At least, until now that was the case. :-)

Remember that you can always introspect the column names, cache them locally, and then create whatever dict you want. That way, it's 100% guaranteed to do the right thing for your application.

Good point. I'll have to do that :-) Should be easy enough, since I know which columns I need to mess with. Sometimes it's the simple solutions...

-----------------------------------------------
Israel Brewster
Systems Analyst II
5245 Airport Industrial Rd
Fairbanks, AK 99709
(907) 450-7293
-----------------------------------------------

--
-- Christophe Pettus
xof(at)thebuild(dot)com<mailto:xof(at)thebuild(dot)com>

In response to

Browse psycopg by date

  From Date Subject
Next Message Karsten Hilbert 2018-04-30 19:32:11 Re: RealDictCursor behavior question
Previous Message Christophe Pettus 2018-04-30 19:24:45 Re: RealDictCursor behavior question