----- Original Message -----
From: "Jim Starkey" <jas@...>
To: <Firebird-Architect@yahoogroups.com>
Sent: Monday, July 07, 2003 5:46 PM
Subject: Re: [Firebird-Architect] Update WHERE CURRENT OF vs.
ResultSet.isLast()


Hi Jim,

> I'm inclinded to blame the JDBC guys, but that's pointless since the
> deed is done.
>
> I'm not going to presume to offer advice on how Firebird should handle
> the problem.
> Netfrastructure, however, handles the ResultSet.isLast() method in
> approximately
> to following manner:
>
> throw new SQLException ("Not Yet Implemented")
>
> A more complete implementation would be:
>
> throw new SQLException ("Not Yet Implemented and Unlikely to
> be Be So")
>
> My reasoning is that positional updates have been part of SQL from day 0
> and are
> semantically significant while ResultSet.isLast() is recent,
> semantically unnecessary,
> and absurdly expensive to implement.
>

I believe those guys were wrong and you are right exactly of the reason you
mentioned.
Usually each data management system (from time 0) have naturally built-in
capability of recognizing
end of data but almost none of them can't recognize whether current record
is last.

Alexander