On 2/15/21 7:39 PM, Mark Rotteveel wrote:
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
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
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
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
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
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
I was experimenting with FETCH ABSOLUTE, and I noticed an interesting
property. It is possible to position beyond the result set (before the
first or after the last row). This position seem to be remembered.
This remembering has no effect for FETCH NEXT / FETCH PRIOR. If
positioned before the
