From: | "emergency(dot)shower(at)gmail(dot)com" <emergency(dot)shower(at)gmail(dot)com> |
---|---|
To: | pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: unusual ResultSet.next() behaviour |
Date: | 2005-07-28 12:56:21 |
Message-ID: | bdf1a098050728055671a8dffa@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
On 7/27/05, Les Carter <carterl(at)newkinetics(dot)com> wrote:
> This is a multi-part message in MIME format. --bound1122440425 Content-Type:
> text/html; charsetiso-8859-1 Content-Transfer-Encoding: quoted-printable
> Consider the following code snippet where rs is a ResultSet object obtained
> from a previous query:
>
> for(int count=0; count!=someValue; count++)
> {
> if(!rs.next()) throw SomeException();
> }
> rs.next();
>
> Pretty simple, just cycle through someValue number of records and then get
> the next record after that.
I suspect that this isn't the code that actually produces the error.
If SomeException() is a constructor, this code wouldn't compile. Could
you post a more complete snippet?
-Alex
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Cramer | 2005-07-28 14:00:46 | Proposed patch for showing originating query on error |
Previous Message | Oliver Jowett | 2005-07-28 10:14:17 | Re: Problems storing timestamps with calendars |