Re: KeyError: self._index[x]

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: tango ward <tangoward15(at)gmail(dot)com>
Cc: "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: KeyError: self._index[x]
Date: 2018-05-08 03:50:14
Message-ID: CAKFQuwbQ4NFdOsnynqK6OAmdbFUsOjT+LtuNdfA6SFqBCQc6YA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Monday, May 7, 2018, tango ward <tangoward15(at)gmail(dot)com> wrote:

>
> cur_t.execute("""
> SELECT TRANSLATE(snumber, ' ', '')
> FROM sprofile """)
>
> # This will result in KeyError
> for row in cur_t:
> print row['snumber']
>
> # This works fine
> for row in cur_t:
> print row[0]
>

So apparently when you execute your query the result has at least one
column but that column isn't named "snumber". I'm sure there is a way in
Python to debug "row" and find out what names it does have. Or maybe
execute the query in something like psql and observe e column name there.

That said, by default the name of columns whose values are derived by a
single function call should be the name of the function. So "translate",
not "snumber" - the latter being consumed by the function. You can as use
"as <alias>" to give it a different fixed name and refer to that.

David J.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2018-05-08 04:06:55 Re: KeyError: self._index[x]
Previous Message tango ward 2018-05-08 03:11:15 Re: KeyError: self._index[x]