| From: | Christophe Pettus <xof(at)thebuild(dot)com> |
|---|---|
| To: | Israel Brewster <ibrewster(at)flyravn(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:24:45 |
| Message-ID: | 40DAA72D-1B8C-44E7-A561-D1B1DF96E440@thebuild.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | psycopg |
> On Apr 30, 2018, at 12:19, Israel Brewster <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.
--
-- Christophe Pettus
xof(at)thebuild(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Israel Brewster | 2018-04-30 19:27:14 | Re: RealDictCursor behavior question |
| Previous Message | Israel Brewster | 2018-04-30 19:19:46 | Re: RealDictCursor behavior question |