Hi,

Generally rowid's are not stable across transactions(Oracle ROWID and
firebird rdb$db_key) and they are not sequentially numbered. I doubt you
want to hold a transaction open while someone peruses a web page of search
results. You appear to have something else in mind for rowid, perhaps a
generated numbering scheme for the ordered set returned by the query?

Why is this a better option than either top or limit (start, end)? It is
certainly more complicated, is there some pressing need for the engine to
do the filtering for you?

thanks
david jencks

On 2001.05.30 19:08:20 -0400 Peter Morris wrote:
> > actually, wouldn't returning a rowid be a better option than first(x)
> or
> > whatever, that way the user can include the rowid in the where clause
> and
> do
> > whatever the hell they want selection wise? select * from blah where
> rowid
> > in (1,3,5,7,9)? I'd think this would be a better option than having it
> as
> an
> > aggregate style function.
>
> I agree 100%.
> TOP etc are very specific, next thing you know you will have PAGE, LAST,
> etc
> etc and that is not good.
> As long as the ROWID is the Rownumber of the current selection and is
> calculated at the end then this would be a brilliant idea.
>
> Pete
> ===
> http://www.HowToDoThings.com
>
>
>
> Community email addresses:
> Post message: IBDI@yahoogroups.com
> Subscribe: IBDI-subscribe@yahoogroups.com
> Unsubscribe: IBDI-unsubscribe@yahoogroups.com
> List owner: IBDI-owner@yahoogroups.com
>
> Shortcut URL to this page:
> http://www.yahoogroups.com/community/IBDI
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
>
>