This is what i found in the specs of the JDBC 3.0 (
http://java.sun.com/products/jdbc/download.html#corespec30)
10.1 Transaction Boundaries and Auto-commit
...
For Insert, Update, Delete, and DDL statements, the statement is
complete as soon
as it has finished executing.
For Select statements, the statement is complete when the associated
result set is
closed. The result set is closed as soon as one of the following occurs:
- all of the rows have been retrieved
- the associated Statement object is re-executed
- another Statement object is executed on the same connection
Looks like last phrase say that i can't have more than one resultSet per
connection at time.
I known that this is not the case with the PostgreSql JDBC driver ( i
made some testes :) ).
This is a feature of the PostgreSql JDBC driver?
Regards.
JP
Michael Paesold wrote:
>João Paulo Caldas Ribeiro wrote:
>
>
>
>
>>I dont know about the JDBC specs but i remember that i used a Oracle
>>JDBC driver that only supported one 1 connection --> 1 resultset at time.
>>I will try to find something about the specs.
>>
>>
>
>
>Probably the specs really don't specify this, but they will require that
>the methods getResultSetConcurrency(), getResultSetHoldability() and
>getResultSetType() return the correct values.
>
>Regards.
>Michael
>
>
>---------------------------(end of broadcast)---------------------------
>TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org
>
>
>
>
--
----------------------------------------------------------------------------
MobiComp - Mobile Computing & Wireless Solutions
phone: +351 253 305 250 fax: +351 253 305 251
web: http://www.mobicomp.com
----------------------------------------------------------------------------
