On 15-02-2021 16:21, Alex Peshkoff via Firebird-devel wrote:
On 2/14/21 4:01 PM, Mark Rotteveel wrote:
For documentation purposes, I was wondering if this was intended
behaviour, both the ability to position beyond the bounds of the
result set using ABSOLUTE, and the remembering of the actual position
for subsequent fetches.
Or if this is just an artifact of implementation, and therefor might
change in a future version and should not be relied on.
For me it sooner looks like a bug in implementation :)
Trying to position in non-existent place should better raise error.
I created http://tracker.firebirdsql.org/browse/CORE-6487
Given ODBC and JDBC specify the behaviour suggested by Dimitry
(positioning immediately before the first row or immediately after the
last row when moving out of bounds), I used that suggestion in the ticket.
Mark
--
Mark Rotteveel
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
