Ok, this makes sense, and is more or less what it does after I fixed it
so you can insert into an empty result set.
Thanks
Dave
On Fri, 2002-08-23 at 14:32, Paul Stead wrote:
> Wouldn't it behave exactly the same as a cursor in a ResultSet before you
> call next() for the first time? Again from JDBC API Tutorial and Reference,
> "when a ResultSet object is first created, the cursor is positioned before
> the first row, so the first call to next() puts the cursor on the first row,
> making it the current row." So wouldn't moveToCurrentRow return the cursor
> to its position before the first row (which now exists, although it didn't
> before)?
>
> Paul
>
> -----Original Message-----
> From: pgsql-jdbc-owner@postgresql.org
> [mailto:pgsql-jdbc-owner@postgresql.org]On Behalf Of Dave Cramer
> Sent: Friday, August 23, 2002 10:38 AM
> To: pstead@elementallogic.com
> Cc: Zengfa Gao; pgsql-jdbc@postgresql.org
> Subject: Re: [JDBC] Proper state after insertRow
>
>
> Ok,
>
> So far this is consistent with what I understand. However there is a
> special case ( there always is ;) ). What if the underlying table has no
> data in it. In this case the cursor is nowhere!
>
> Dave
> On Fri, 2002-08-23 at 12:24, Paul Stead wrote:
> > Dave,
> >
> > No expert here, but according to JDBC API Tutorial and Reference, 2nd Ed,
> > from the Java Series:
>
> <<< snip >>>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly
>
>
