-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Query Validation in readonly mode possible? #987
Comments
If you add |
Hmm, that's weird. It's definitely not working for me with
The directory itself is also not writable, so perhaps this is a misleading error and what's actually failing is some kind of locking or the WAL. For example, even accessing it with
The documentation says that this flag is for when the database file exists on read-only media. Still trying to dig into the code and see if supporting that flag would help here, but wanted to give an update. |
I put a patchset that seems to solve my problem in master...djmarcin:immutable It appears to me that the "immutable" parameter only works when sent on the connection URI and there's no flag to enable it. I don't know how switching back to the URI affects any of the other connection options, so I'm not sure if this is mergeable or not. Let me know if you'd like me to send it as a PR, though. |
@djmarcin if you want to add it as a flag to |
I can confirm that yes, I agree with @abonander. We would accept a PR for that patch, yes. |
I'm trying to resolve an issue where my build system is generating the schema for query validation as a readonly sqlite file. Is it possible for query validation to operate on sqlite in readonly mode?
If not, perhaps an option to copy the database schema to an in-memory database for validation would be a possibility?
The text was updated successfully, but these errors were encountered: