Re: Connections/Statements/ResultSets (Was: Re: Pooling

You can definately have more than one result set open per connection, as
long as you don't have more than 1 result set per statement. If and when
cursor backed result sets get implemented then you will still be able
to. The cursor will only be used if you explicitly call setFetchSize

Dave
On Fri, 2002-08-30 at 11:35, João Paulo Caldas Ribeiro wrote:
> I underestand you: I'm confused too. :)
>
> But at the moment i can tell you that postgresql support  1 connection
> --> more than 1 resultset at time.
> I have tested this case explicitly and it really work .
>
> I will try to put the question to the JDBC forum.  I hope they can
> explain this.
>
> Regards.
> JP
>
> Thomas O'Dowd wrote:
>
> >Hmmm, the title is "Transaction Boundaries and Auto-commit", this seems
> >to apply in the case when autocommit is on??? In an earlier mail you
> >sent from the spec it clearly states that you can have multiple
> >ResultSets open and processed concurrently on the same connection "A.1.6
> >Support Multi-threading". Hmmm. Confusing... I must RTFM and make up my
> >own mind.
> >
> >In either case, it would be nice to have a nice big red flag waved on
> >the list if the multiple ResultSet thing is going to go away. It will
> >definitely break a lot of my code and I'm not so sure its so wrong.
> >
> >Tom.
> >
> >On Fri, 2002-08-30 at 23:41, João Paulo Caldas Ribeiro wrote:
> >
> >
> >>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
> >>----------------------------------------------------------------------------
> >>
> >>
> >>
> >>
> >>
> >>---------------------------(end of broadcast)---------------------------
> >>TIP 2: you can get off all lists at once with the unregister command
> >>    (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)
> >>
> >>
>
>
> --
> ----------------------------------------------------------------------------
> MobiComp - Mobile Computing & Wireless Solutions
> phone: +351 253 305 250     fax: +351 253 305 251
> web: http://www.mobicomp.com
> ----------------------------------------------------------------------------
>
>
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org
>
>