Обсуждение: scollable result sets
Are they broken in 8.1? I no matter what I do Postgresl throws an exception with calls to functions like previous() and last().
x_conn.prepareCall ( os_query, ResultSet.TYPE_SCROLL_INSENSITIVE, ResultSet.CONCUR_READ_ONLY );
x_conn.prepareCall ( os_query, ResultSet.TYPE_SCROLL_INSENSITIVE, ResultSet.CONCUR_READ_ONLY );
--
Matt,
no they are not broken.
But AFAIK a ScrollableResultSet with Postgres JDBC supports forward only. Try again with different settings and of course don't call previous().
If you need scroll back functionality you could use cursors.
Christian
Von: pgsql-jdbc-owner@postgresql.org [mailto:pgsql-jdbc-owner@postgresql.org] Im Auftrag von Matt Chambers
Gesendet: Dienstag, 5. September 2006 23:16
An: pgsql-jdbc@postgresql.org
Betreff: [JDBC] scollable result sets
Are they broken in 8.1? I no matter what I do Postgresl throws an exception with calls to functions like previous() and last().
x_conn.prepareCall ( os_query, ResultSet.TYPE_SCROLL_INSENSITIVE, ResultSet.CONCUR_READ_ONLY );--
************************************************
The information contained in, or attached to, this e-mail, may contain confidential information and is intended solely for the use of the individual or entity to whom they are addressed and may be subject to legal privilege. If you have received this e-mail in error you should notify the sender immediately by reply e-mail, delete the message from your system and notify your system manager. Please do not copy it for any purpose, or disclose its contents to any other person. The views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of the company. The recipient should check this e-mail and any attachments for the presence of viruses. The company accepts no liability for any damage caused, directly or indirectly, by any virus transmitted in this email.
************************************************
I read someplace that the CVS version may support it. Unfortunately, gborg seems to be down for the past day or so. Looking through the code, I see things like:
while (x_rset.next()) {
x_rset.previous()
function_that_calls_next(x_rset)
}
Is there a better way to do this? With result pointers from other languages, like perl, python, php, I know the size of the result so I can choose the type of loop I want to use. Is there a better way to loop through a result set and have a another function call next?
Matt
Koth, Christian (DWBI) wrote:
Matt,
no they are not broken.
But AFAIK a ScrollableResultSet with Postgres JDBC supports forward only. Try again with different settings and of course don't call previous().
If you need scroll back functionality you could use cursors.
Christian
Von: pgsql-jdbc-owner@postgresql.org [mailto:pgsql-jdbc-owner@postgresql.org] Im Auftrag von Matt Chambers
Gesendet: Dienstag, 5. September 2006 23:16
An: pgsql-jdbc@postgresql.org
Betreff: [JDBC] scollable result sets
Are they broken in 8.1? I no matter what I do Postgresl throws an exception with calls to functions like previous() and last().
x_conn.prepareCall ( os_query, ResultSet.TYPE_SCROLL_INSENSITIVE, ResultSet.CONCUR_READ_ONLY );--
| |
Koth, Christian (DWBI) wrote: > Matt, > no they are not broken. Actually I think CallableStatements are (it's already fixed in CVS) > But AFAIK a ScrollableResultSet with Postgres JDBC supports forward > only. This is incorrect. If it's FORWARD_ONLY, it's not scrollable by definition. -O