From: | "Dave Cramer" <Dave(at)micro-automation(dot)net> |
---|---|
To: | "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | <pgsql-jdbc(at)postgresql(dot)org> |
Subject: | Re: driver fails to handle strings in query statements properly |
Date: | 2001-10-03 01:11:49 |
Message-ID: | 008d01c14ba8$6178f330$8201a8c0@inspiron |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
As I said, I have no idea how the backend handles it when it is quoted.
You mention that it's not a column reference, but it does get data from
the id column?
Dave
-----Original Message-----
From: pgsql-jdbc-owner(at)postgresql(dot)org
[mailto:pgsql-jdbc-owner(at)postgresql(dot)org] On Behalf Of Tom Lane
Sent: October 2, 2001 6:16 PM
To: Dave(at)micro-automation(dot)net
Cc: 'Barry Lind'; pgsql-jdbc(at)postgresql(dot)org
Subject: Re: [JDBC] driver fails to handle strings in query statements
properly
"Dave Cramer" <Dave(at)micro-automation(dot)net> writes:
> I tried it on a table which id was an int
> Using "select 'id' as xxx from ..." Returns xxx as an unknown type
> Using "select id as xxx from... " returns xxx as an int I have no idea
> how the backend handles this, but if it can figure it out in one
> instance why can't it figure it out when I put single quotes around
> it?
Uh ... when you put single quotes around it, it's a literal, not a
column reference ... and whatever one might think about 'id', it's
certainly not an integer.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?
From | Date | Subject | |
---|---|---|---|
Next Message | Barry Lind | 2001-10-03 01:13:14 | Re: LOCK TABLE oddness in PLpgSQL function called via JDBC |
Previous Message | Barry Lind | 2001-10-03 01:03:26 | Re: LOCK TABLE oddness in PLpgSQL function called via JDBC |