Ok I understand now.
It was difficult to see why SQLite would ever choose to return rows in a
different order than the order in which they were stored if the SELECT does not
specify an ORDER until Dr. Hipp explained that it could get the requested
columns from a separate index instead of the
On 5/1/19, Tom Bassel wrote:
> Hi,
>
> In this page in the docs: https://sqlite.org/queryplanner.html#searching
>
> it says:
> "The rows are logically stored in order of increasing rowid"
>
> Would this imply that executing a SELECT would always return the rows in
> order or increasing rowid?
>
>
On Wednesday, 1 May, 2019 15:56, Tom Bassel wrote:
>In this page in the docs:
>https://sqlite.org/queryplanner.html#searching
>it says:
>"The rows are logically stored in order of increasing rowid"
>Would this imply that executing a SELECT would always return the rows
>in order or increasing
Hi,
In this page in the docs: https://sqlite.org/queryplanner.html#searching
it says:
"The rows are logically stored in order of increasing rowid"
Would this imply that executing a SELECT would always return the rows in order
or increasing rowid?
So that a "SELECT * from MyTable" would return
4 matches
Mail list logo