Hi Dave/Tom,
Thanks very much for the suggestion. The problem was beacuse the paramaters
in the where clause were not getting replaced with the actual values. This I
could figure out from the log and have corrected the logic to handle it
properly. Now the queries are working fine.
Thanks & Regards,
Gautham
----- Original Message -----
From: "Dave Cramer" <Dave@micro-automation.net>
To: "Tom Lane" <tgl@sss.pgh.pa.us>
Cc: "Gautham S. Rao" <gautam.rao@tatainfotech.com>;
<pgsql-jdbc@postgresql.org>
Sent: Friday, April 05, 2002 10:22 PM
Subject: Re: [JDBC] JDBC Driver Problem
> This would be my guess too. It would make sense that the code that is
> checking for escape sequences is broken
>
> Dave
>
> On Fri, 2002-04-05 at 11:09, Tom Lane wrote:
> > "Gautham S. Rao" <gautam.rao@tatainfotech.com> writes:
> > > This query returns 4 records when executed from the back end which is
the
> > > desired result. But when it is executed using the JDBC driver for
postgreSQL
> > > 7.1 and JDK 1.2, it returns only 3 records. This is the result of the
first
> > > query excluding the union. So it appears as if only the first part of
the
> > > query is working through the JDBC driver.
> >
> > Could the driver be dropping part of the query? I suggest turning on
> > query logging at the backend (restart postmaster with -d2 switch, or
> > set debug_print_query = true in postgresql.conf) and then look in the
> > postmaster log to see exactly what query is being sent by JDBC.
> >
> > regards, tom lane
> >
> > ---------------------------(end of broadcast)---------------------------
> > TIP 6: Have you searched our list archives?
> >
> > http://archives.postgresql.org
> >
> >
>
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org
>
