Subject | Re: [IBDI] Re: FIRST/TOP/LIMIT/ROWNUM - Proposals |
---|---|
Author | Lester Caine |
Post date | 2001-06-07T19:23:49Z |
Just to muddy the waters.
I can see the need for FIRST n, and it would help me with a
number of routines, but what about AFTER <bookmark> rather
than between some arbitary numbers..
This I think ties up with what Jason suggested earlier. Once
you have displayed the first 10 records, you get the next
ten by looking 'after' the bookmark of the last record
displayed. This has the advantage that if one or more of the
first n records are deleted, then a continuous display of
information is maintained.
WHERE x > <bookmark> would work if the database is designed
right in the first place, so that all this talk of ROWNUM is
not required. I view ROWNUM in the same light as GOTO - the
lasy way of programming. Design things right in the first
place and you do not need either.
--
Lester Caine
-----------------------------
L.S.Caine Electronic Services
I can see the need for FIRST n, and it would help me with a
number of routines, but what about AFTER <bookmark> rather
than between some arbitary numbers..
This I think ties up with what Jason suggested earlier. Once
you have displayed the first 10 records, you get the next
ten by looking 'after' the bookmark of the last record
displayed. This has the advantage that if one or more of the
first n records are deleted, then a continuous display of
information is maintained.
WHERE x > <bookmark> would work if the database is designed
right in the first place, so that all this talk of ROWNUM is
not required. I view ROWNUM in the same light as GOTO - the
lasy way of programming. Design things right in the first
place and you do not need either.
--
Lester Caine
-----------------------------
L.S.Caine Electronic Services