Re: [sqlite] Error when renaming a table when an invalid view exists in the schema

Thanks Keith. LEGACY_ALTER_TABLE=ON lets me change the table name without error. But the docs say "New applications should leave this flag turned off." Is there any other way of checking if the schema is invalid besides attempting to change the name of a table? I went through the pragmas and

[sqlite] Error when renaming a table when an invalid view exists in the schema

Hello again everyone, I went through the ALTER TABLE docs but could not find anything describing this behavior: SQLite version 3.29.0 2019-04-27 20:30:19 Enter ".help" for usage hints. Connected to a transient in-memory database. Use ".open FILENAME" to reopen on a persistent database. sqlite>

Re: [sqlite] logically stored rows

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

[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

Re: [sqlite] WITHOUT ROWID tables with a ROWID

Ah I see now. Sorry I should have read the docs more carefully -- it is working according to spec in all cases. Great answers. Thanks guys! Tom ___ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org

[sqlite] WITHOUT ROWID tables with a ROWID

Hi, this is my first post to this group. I am not trying to be difficult. I work on an app that uses SQLite as the underlying database engine. At one time years ago I remember assuming that the ROWID column in a table in SQLite would always be an integer. However, I can see a user who is not