Please don't try to go there. Relying on the implicit visitation order is a frequent cause of code breaking when the query planner changes the plan (eg .in a new SQLite release or if the "shape" of your data changes and ANALYZE is run).
If your application depends on the rows being returned in a specific order from a specific query, then add an ORDER BY clause. If that happens to be the visitation order, no cost will be incurred; if not, then a slowdown (with correct results) is better than incorrect results (at the same speed). -----Ursprüngliche Nachricht----- Von: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] Im Auftrag von Tom Bassel Gesendet: Mittwoch, 01. Mai 2019 23:56 An: sqlite-users@mailinglists.sqlite.org Betreff: [EXTERNAL] [sqlite] logically stored rows 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 all the rows in ROWID order because that is how they are stored. Thanks Tom _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users ___________________________________________ Gunter Hick | Software Engineer | Scientific Games International GmbH | Klitschgasse 2-4, A-1130 Vienna | FN 157284 a, HG Wien, DVR: 0430013 | (O) +43 1 80100 - 0 May be privileged. May be confidential. Please delete if not the addressee. _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
