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
{{ message }}
Repository navigation
Breaking Changes between versions 1.1.3 and 1.60 #329
There seems to be some disagreement about what constitutes a valid SQLite database table name https://stackoverflow.com/questions/3694276/what-are-valid-table-names-in-sqlite, but I have been using for years names that start with numbers so unfortunate for me this breaks my code. I'll stick with 1.1.3 for now and keep a look out for updates.
Thanks for the report. The SQLite.tables return type change can't be undone now without breaking current users, sorry. Table names starting with a digit work on current versions: SQLite.tables(db) and SQLite.columns(db, "1isanumber") both return the table.
Activity
qSeven commentedon Mar 20, 2023
Another issue that breaks my code is that SQLite.tables(db) can not read a database with table names starting with numbers in 1.6.0, but can in 1.1.3
This can be detected with
or with
in 1.6.0
In 1.1.3 this returns
["1isanumber"]In 1.6.0 this returns
There seems to be some disagreement about what constitutes a valid SQLite database table name https://stackoverflow.com/questions/3694276/what-are-valid-table-names-in-sqlite, but I have been using for years names that start with numbers so unfortunate for me this breaks my code. I'll stick with 1.1.3 for now and keep a look out for updates.
quinnj commentedon Sep 30, 2026
Thanks for the report. The
SQLite.tablesreturn type change can't be undone now without breaking current users, sorry. Table names starting with a digit work on current versions:SQLite.tables(db)andSQLite.columns(db, "1isanumber")both return the table.