For what its worth Dave, there are two places in my code where it the exception occurs and with both of them there is a prior statement to lock the table in share row exclusive mode. ie:
Statement st = db.createStatement();
st.executeUpdate("lock table tablex in share row exclusive mode");
String statment = "select col1 from tablex where col2 = ?";
PreparedStatement ps = db.prepareStatement(statement);
ps.setString(1, col2text);
ResultSet rs = ps.executeQuery(); // <- Exception thrown here
It may be coincidental but I thought it would be remiss of me to leave it out.
Tim.
Dave Cramer wrote:
Yes, I can confirm that it does indeed throw an exception. I will have a look
at this shortly.
Thanks,
Dave
> -----Original Message-----
> From: pgsql-jdbc-owner@postgresql.org
> [mailto:pgsql-jdbc-owner@postgresql.org] On Behalf Of Tim Lewis
> Sent: Tuesday, March 19, 2002 7:01 PM
> To: pgsql-jdbc@postgresql.org
> Subject: [JDBC] "No results were returned by the query" exceptions
>
>
> Hi people,
>
> Am I correct in assuming that the new driver now throws an
> exception when a "No results were returned by the query"
> occurs for a prepared sql statement. I have recently
> upgraded the driver from 7.1 to 7.2 and my application now
> throws this exception when a query returns no rows in the result set.
>
> Could someone clarify this with me.
>
> Thanks,
>
> Tim Lewis
>
>
> ---------------------------(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
--
Tim Lewis
Senior Software Engineer
Hitwise
Level 7/580 St Kilda Road
Melbourne, Victoria 3004
Phone : +61-3-8530-2400
Direct: +61-3-8530-2402
Fax : +61-3-9529-8907
Mobile: 0414 726 899
Email : tim.lewis@hitwise.com