I'm going to vote for option ii, since SKIP, TAKE, and SELECT are
similar in English. The syntax doesn't say SELECTING, which would be
equivalent IMHO.
Juts to avoid any complaints about completeness,
Option iv: SELECT ... FROM ... WHERE ... ORDER BY ... SKIPPING x TAKING y
Patrick
On Sun, Feb 6, 2011 at 11:49 AM, Patrick Earl <[email protected]> wrote:
> So we have:
>
> Option i: SKIPPING x TAKING y SELECT ... FROM ... WHERE ... ORDER BY ...
> Option ii: SKIP x TAKE y SELECT ... FROM ... WHERE ... ORDER BY ...
> Option iii: SELECT ... FROM ... WHERE ... ORDER BY ... SKIP x TAKE y
>
> For the first, people would need to get the spelling right on
> skipping, unless we just supported both versions (skipping and
> skiping).
>
> Patrick
>
> On Sun, Feb 6, 2011 at 11:42 AM, Stephen Bohlen <[email protected]> wrote:
>> I really like that structure.
>>
>> +1
>>
>> Steve Bohlen
>> [email protected]
>> http://blog.unhandled-exceptions.com
>> http://twitter.com/sbohlen
>>
>>
>> On Sun, Feb 6, 2011 at 1:33 PM, Fabio Maulo <[email protected]> wrote:
>>>
>>> Put it at the begin of the query.
>>> It will be clear and, over all, more easy to implement (read it as
>>> 'grammar').
>>> Examples:
>>> SKIPING 50 TAKING 25 select e.Name, e.Surname from Employee e ......
>>> SKIPING 50 TAKING 25 from Employee
>>> from Users u where u.Employee in (TAKING 25 from Employee e order by
>>> e.Salary desc)
>>> On Sun, Feb 6, 2011 at 2:23 PM, Patrick Earl <[email protected]> wrote:
>>>>
>>>> Based on the feedback so far, it seems like the simpler syntax is more
>>>> desired. What are people's preferences around the following two
>>>> options?
>>>>
>>>> SKIP x TAKE y
>>>> OFFSET x LIMIT y
>>>>
>>>> Seems like Fabio and Diego prefer the first two. I'm also liking the
>>>> skip and take a bit more at this point, since it's more descriptive,
>>>> despite being less standard from a SQL perspective. Other's thoughts?
>>>>
>>>> Patrick Earl
>>>
>>>
>>>
>>> --
>>> Fabio Maulo
>>>
>>
>>
>
