Hi Fabian,
Thank you for your replay.
On Thu, Oct 12, 2017 at 4:18 PM, Fabian Hueske wrote:
> Hi John,
>
> I agree that the Table.limit(offset) method is confusing and that the
> semantics should rather be to specify the fetch parameter than the offset
> parameter.
> However, we can not easil
Hi John,
I agree that the Table.limit(offset) method is confusing and that the
semantics should rather be to specify the fetch parameter than the offset
parameter.
However, we can not easily change the behavior of an existing function. The
only way to evolve the functionality is to add new methods
Now the Table don't support the limit operator without orderBy operator.
On Thu, Oct 12, 2017 at 2:30 PM, John Fang wrote:
> Hi,
>
>In order to support ORDER BY OFFSET FETCH, we add the Table API
> `limit`. But the api is confused. For example: "table.limit(3)" means
> unlimited number of
Hi,
In order to support ORDER BY OFFSET FETCH, we add the Table API
`limit`. But the api is confused. For example: "table.limit(3)" means
unlimited number of records beginning with the 4th record. In fact I prefer
"table.limit(3)" means taking the first `3` rows.
So I prefer to use the API "
