> > Yes you are wrong. As I and others have already answered you tables
> > are unordered sets of rows. There is no position. Postion comes to
> > play on your client side when you see your data in some nice grid
>
> Ok.
> So, how does first/skip works?
>

It works exactly as described in the documentation. And that specification
doesn't meet your requirements. That means you will not use first/skip or
rows syntax.

I have offered you solution, which you haven't commented on. Another
solution would be to write a stored procedure which would take string
parameter (list of values), parse it and in for select loop return only
those rows you requested. I think that's even worse idea than the one i
already gave you.

The point is that your requirements are not suited to relation model. Now,
you can implement one of those solution I gave you, and they will work fine
with "small" sets and neither is scalable. But be warned that's not how
systems should be designed.
Or, instead of asking how could you select some records based on their
position, you could describe what you are trying to achieve and what is your
current database design, and we might be able to help you.

Sasha