You only need to know two things from the client. A bookmark to a record on
the server and what the ordering is.
I think you are trying to make this too difficult for yourself.

Jason Wharton
CPS - Mesa AZ
http://www.ibobjects.com

----- Original Message -----
From: "Peter Morris" <pmorris@...>
To: <IBDI@yahoogroups.com>
Sent: Monday, June 04, 2001 9:50 AM
Subject: Re: [IBDI] Firebird 1


> > A typical relational table has a PK. A PK is unique by nature. If your
> > tables don't implement any concept of basic relational theory, locating
an
> > exact record is only one of the many problems your db design will have.
>
> My problem isn't that, my problem is that the result will not be ordered
by
> any 1 specific field every time someone requests the list (may be name, or
a
> date etc), but once the query is decided it will remain the same for the
> whole list so the results will always be in the same order.
>
> I could request the whole result set, and then use next until I reach the
> last record previously displayed, but this way I would have to request a
lot
> of data just to throw it away.
>
> Pete
>
>
> 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/
>
>