Unusable resultset

From: Matt Mello <alien(at)spaceship(dot)com>
To: pgsql-jdbc(at)postgresql(dot)org
Subject: Unusable resultset
Date: 2003-01-29 05:55:29
Message-ID: 3E376CD1.8060106@spaceship.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

I just did a query that would have returned impossible amounts of data,
eg: select * from BIGtable. I am porting from Informix to Postgresql,
and I guess I have been spoiled by the IFX JDBC drivers, which return
only as much data, relatively speaking, as is needed. When the IFX JDBC
driver runs out of data, it asks the backend for more data. Apparently
the backend caches the results instead of shoving it all down the socket
to the JDBC driver all at once. (Oh, how I wish PG JDBC did that.)

Anyway, when I did the above, I got back a null resultset. I don't even
think it threw an exception (but I will try to check on that). All of
that is fine and can be dealt with. My real problem is that the
connection is no longer usable, as ANY query I perform throws a
"postgresql.con.type" exception.

Why does it do that, and what is a "type" exception?

I now catch this specific exception as an indication that the connection
is bad, after which I close it, but it sure is annoying to have to put
driver-specific code in my java codebase. :(

--
Matt Mello

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message Curt Sampson 2003-01-29 06:43:30 Re: JDBC access with md5 password
Previous Message Tony Grant 2003-01-28 23:08:58 Re: where to put postgresql.jar in Mac OS X