Re: Connections/Statements/ResultSets (Was: Re: Pooling
От | Dave Cramer |
---|---|
Тема | Re: Connections/Statements/ResultSets (Was: Re: Pooling |
Дата | |
Msg-id | 1030701016.12890.424.camel@inspiron.cramers обсуждение исходный текст |
Ответ на | Connections/Statements/ResultSets (Was: Re: Pooling Prepared Statements) ("Michael Paesold" <mpaesold@gmx.at>) |
Список | pgsql-jdbc |
The spec probably doesn't say anything but; with the way pg's driver is currently written you can have as many resultsets/statements open as you want. This is because the driver will read them all in when you do an executeXXX. There is a plan however to move to a cursor backed result set which will change the above statement. This is because a cursor must be executed within a transaction, and you can only have one transaction open per resultset. I suppose it's possible to still open a non-cursor based resultset while the transaction is open? Dave On Fri, 2002-08-30 at 04:34, Michael Paesold wrote: > Curt Sampson wrote: > > > On Thu, 29 Aug 2002, Michael Paesold wrote: > > > > > So it's not 1 connection -> 1 resultset at a time, but 1 statement -> 1 > > > resultset at a time. > > > > Sorry, but there are many JDBC drivers out there that allow only > > one resultset on a connection at a time. You may get more than one > > per connection with some drivers, but that's not portable. > > > > cjs > > > Does anyone of you know exactly, what the JDBC specification says about > more than one result set per connection at a time? > > If not, can you give me a URL where I can have a look at the specs myself? > > Michael > > > ---------------------------(end of broadcast)--------------------------- > TIP 2: you can get off all lists at once with the unregister command > (send "unregister YourEmailAddressHere" to majordomo@postgresql.org) > >
В списке pgsql-jdbc по дате отправления: