From: | Patrick Tucker <tuckerpmt(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #6727: Column does not exist exception has no error code |
Date: | 2012-07-11 18:10:35 |
Message-ID: | CAOmDbN7Yw4qndPzk-nxmdcQmHtO9fgpxTdPcOkEeGcRNzYUpVw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Interesting, the test case that I ran was performing a simple SQL statement
like the following: select "a" from table
I wonder if the version of the driver I am using needs to be updated or
even the database?
Thanks,
Pat
On Wed, Jul 11, 2012 at 1:43 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> tuckerpmt(at)gmail(dot)com writes:
> > The SQLException that is thrown when performing a query that has a column
> > name that is not valid, does not exist, does not contain an error
> > code.
>
> Could you provide a specific example? When I try this I see an error
> code, 42703:
>
> regression=# \set VERBOSITY verbose
> regression=# select nosuchcol from int8_tbl;
> ERROR: 42703: column "nosuchcol" does not exist
> LINE 1: select nosuchcol from int8_tbl;
> ^
> LOCATION: transformColumnRef, parse_expr.c:766
>
> There may indeed be someplace where the errcode was forgotten, but
> without a concrete example it's hard to find where.
>
> regards, tom lane
>
From | Date | Subject | |
---|---|---|---|
Next Message | Patrick Tucker | 2012-07-11 18:24:09 | Re: BUG #6727: Column does not exist exception has no error code |
Previous Message | Tom Lane | 2012-07-11 17:43:19 | Re: BUG #6727: Column does not exist exception has no error code |