Re: driver fails to handle strings in query statements properly - Mailing list pgsql-jdbc

From Dave Cramer
Subject Re: driver fails to handle strings in query statements properly
Date
Msg-id 008d01c14ba8$6178f330$8201a8c0@inspiron
Whole thread Raw
In response to Re: driver fails to handle strings in query statements properly  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: driver fails to handle strings in query statements properly (ignore my last post)
List 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@postgresql.org
[mailto:pgsql-jdbc-owner@postgresql.org] On Behalf Of Tom Lane
Sent: October 2, 2001 6:16 PM
To: Dave@micro-automation.net
Cc: 'Barry Lind'; pgsql-jdbc@postgresql.org
Subject: Re: [JDBC] driver fails to handle strings in query statements
properly


"Dave Cramer" <Dave@micro-automation.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?

http://archives.postgresql.org



pgsql-jdbc by date:

Previous
From: Dave Harkness
Date:
Subject: Re: LOCK TABLE oddness in PLpgSQL function called via
Next
From: Hiroshi Inoue
Date:
Subject: Re: LOCK TABLE oddness in PLpgSQL function called via JDBC