Re: executeQuery returns postgresql.stat.result

From: "Nico" <nicohmail-postgresql(at)yahoo(dot)com>
To: pgsql-jdbc(at)postgresql(dot)org
Subject: Re: executeQuery returns postgresql.stat.result
Date: 2005-05-01 19:00:37
Message-ID: d5391g$j8p$1@news.hub.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

I noticed it. Because the exception was captured, it didn't show a
stacktrace.
I solved it and it works fine now. Thanks.

Nico.

"Kris Jurka" <books(at)ejurka(dot)com> schreef in bericht
news:Pine(dot)BSO(dot)4(dot)56(dot)0505011302210(dot)22827(at)leary(dot)csoft(dot)net(dot)(dot)(dot)
>
>
> On Sun, 1 May 2005, Nico wrote:
>
>> The batch statement is ONLY used in case of an update, insert or delete
>> command. When a select command is used, there is no batch used, as you
>> can see in my code.
>
> No, I can't see that. You have a case mismatch between your sql and your
> test. A simple examination of the stacktrace from this error would
> clearly show the wrong code being called.
>
> Kris Jurka
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
> (send "unregister YourEmailAddressHere" to majordomo(at)postgresql(dot)org)
>

In response to

Browse pgsql-jdbc by date

  From Date Subject
Next Message Martin Keller 2005-05-02 11:22:49 Re: Problems storing timestamps with calendars
Previous Message Kris Jurka 2005-05-01 18:04:14 Re: executeQuery returns postgresql.stat.result