-
-
Notifications
You must be signed in to change notification settings - Fork 695
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Invalid SQL: "no such table: pragma_database_list" on database page #1276
Comments
That's really odd. What version of SQLite are you using on the server? You can tell by visiting |
I just managed to replicate this bug on Glitch: https://nicar-2020.glitch.me/data
https://nicar-2020.glitch.me/-/versions says: {
"python": {
"version": "3.7.10",
"full": "3.7.10 (default, Feb 20 2021, 21:21:24) \n[GCC 5.4.0 20160609]"
},
"datasette": {
"version": "0.55"
},
"asgi": "3.0",
"uvicorn": "0.13.4",
"sqlite": {
"version": "3.11.0",
"fts_versions": [
"FTS4",
"FTS3"
],
"extensions": {
"json1": null
},
"compile_options": [
"ENABLE_COLUMN_METADATA",
"ENABLE_DBSTAT_VTAB",
"ENABLE_FTS3",
"ENABLE_FTS3_PARENTHESIS",
"ENABLE_JSON1",
"ENABLE_LOAD_EXTENSION",
"ENABLE_RTREE",
"ENABLE_UNLOCK_NOTIFY",
"ENABLE_UPDATE_DELETE_LIMIT",
"HAVE_ISNAN",
"LIKE_DOESNT_MATCH_BLOBS",
"MAX_SCHEMA_RETRY=25",
"OMIT_LOOKASIDE",
"SECURE_DELETE",
"SOUNDEX",
"SYSTEM_MALLOC",
"TEMP_STORE=1",
"THREADSAFE=1"
]
}
} That's SQLite 3.11.0 from 2016-02-15 with no FTS5. |
The Glitch server logs showed:
|
Here's where I run that: datasette/datasette/database.py Lines 249 to 253 in 6f41c8a
That's from when I added the |
Aha! https://www.sqlite.org/pragma.html says:
|
Testing this on Glitch by adding |
Fantastic. Thank you! |
Don't think this has been covered here yet. I'm a little stumped with this one and can't tell if it's a bug or I have something misconfigured.
Oddly, when running locally the usual list of tables populates (i.e. at /charts a list of tables in charts.db). But when on the web server it throws an Invalid SQL error and "no such table: pragma_database_list" below.
All the url endpoints seem to work fine aside from this - individual tables (/charts/chart_one), as well as stored queries (/charts/query_one).
Not sure if this has anything to do with upgrading to Datasette 0.55, or something to do with our setup, which uses a metadata build script similar to the one for the 538 server, or something else.
The text was updated successfully, but these errors were encountered: