You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am experiencing an issue with the OctoSQL tool when using the offset clause in a query with a CSV file. When I run a query such as:
./octosql "select Period from overseas.csv order by Period limit 10 offset 10"
The offset clause seems to be ignored and I get the same 10 lines regardless of the value of the offset. I have tried running the same query without the order by clause, but the behavior persists.
I expect the output to return the first ten rows with an offset of 0, the rows 11 to 20 with an offset of 10, and so on. However, this is not the case.
Additionally, I have noticed that queries with an invalid offset value do not raise any errors. For example:
./octosql "select Period from overseas.csv order by Period limit 10 offset imnotanumber"
I would expect an error to be raised when an invalid offset value is provided.
This issue occurs with any CSV file.
Thank you for your time.
The text was updated successfully, but these errors were encountered:
I am experiencing an issue with the OctoSQL tool when using the offset clause in a query with a CSV file. When I run a query such as:
The offset clause seems to be ignored and I get the same 10 lines regardless of the value of the offset. I have tried running the same query without the order by clause, but the behavior persists.
I expect the output to return the first ten rows with an offset of 0, the rows 11 to 20 with an offset of 10, and so on. However, this is not the case.
Additionally, I have noticed that queries with an invalid offset value do not raise any errors. For example:
I would expect an error to be raised when an invalid offset value is provided.
This issue occurs with any CSV file.
Thank you for your time.
The text was updated successfully, but these errors were encountered: