On 15-02-2021 16:45, Dimitry Sibiryakov wrote:
15.02.2021 16:21, Alex Peshkoff via Firebird-devel wrote:
Trying to position in non-existent place should better raise error.
According to ODBC (which is the most-established DB API) specs of
SQLFetchScroll() function fetching beyond record set must end up to
fixed "before start"/"after end" positions and return SQL_NO_DATA.
I could live with that behaviour. Because that would match with how
FETCH NEXT / PRIOR currently already behave when positioned further out
of bounds. Right now, it is only FETCH RELATIVE where the actual amount
you're out of bounds matters, and having FETCH RELATIVE 1 behave as
FETCH NEXT and FETCH RELATIVE -1 as FETCH PRIOR sounds reasonable.
Mark
--
Mark Rotteveel
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
