| From: | Oliver Jowett <oliver(at)opencloud(dot)com> |
|---|---|
| To: | jonathan(dot)lister(at)vaisala(dot)com |
| Cc: | pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: JDBC Scrollable ResultSet |
| Date: | 2003-09-14 01:29:44 |
| Message-ID: | 20030914012942.GE12964@opencloud.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
On Sat, Sep 13, 2003 at 11:03:02AM +0300, jonathan(dot)lister(at)vaisala(dot)com wrote:
> Are first() and previous() fully implemented?
>
> My tests indicate that first() will correctly return false if the
> resultSet(TYPE_SCROLL_INSENSITIVE,CONCUR_READ_ONLY) is empty, but if I have
> called next() several times on a non-empty resultSet then a call to first()
> doesn't seem to have any effect, even though it returns true.
>
> pg 7.3.2, latest stable pg73jdbc2
>
> Does anyone have a smart workaround?
Are you also using setFetchSize()? I've noticed that the cursor-based-fetch
implementation that gets used with a non-zero fetchsize doesn't look like it
will work correctly with scrollable resultsets.
-O
| From | Date | Subject | |
|---|---|---|---|
| Next Message | jonathan.lister | 2003-09-14 06:28:43 | Re: JDBC Scrollable ResultSet |
| Previous Message | Oliver Jowett | 2003-09-14 00:16:58 | Re: Specification of "/" in the host name (for Unix socket support) |