-
Notifications
You must be signed in to change notification settings - Fork 599
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
SQLException when calling setReadOnly #247
Comments
It seems PRAGMA query_only may be used. |
Any plans to address this in the near future? :) |
We hit this as well with HikariCP. HikariCP is explicitly setting readOnly to a value which it chooses, which may differ from the setting of the underlying DataSource. The solution was to tell HikariCP to leave it alone, in our case, by setting HCP's readOnly flag to the same as that of SQLite. There is an argument to say that the result of an "advisory" (doc: "hint") call to sqlite should not be fatal. However, the doc on setReadOnly permits exceptions to be thrown under somewhat loosely defined circumstances ("if a database error occurs"). No strong conclusion about validity. |
I ran into this at work, and the
|
This also worked (in 3.28.0), and was considerably simpler:
|
Would be fixed by #432 i suppose |
This is an unresolved bug (2014) migrated from bitbucket. I did not find it in github issues and it is still a problem.
Since version 3.7.15-M1, we see the following exception:
Such behaviour differs from other JDBC drivers.
see also:
http://stackoverflow.com/questions/23390278/scalikejdbc-sqlite-cannot-change-read-only-flag-after-establishing-a-connecti
The text was updated successfully, but these errors were encountered: