-
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
SqliteConnectOptions::filename() memory fix (#3136) #3137
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This will erase the in_memory
flag if the filename is not :memory:
but that would break usage of in-memory databases with shared cache (see the description of the SQLITE_OPEN_MEMORY
flag): https://www.sqlite.org/c3ref/open.html
Additionally, the docs for filename()
need to be updated to describe the new behavior.
@hoxxep are you planning on addressing my review comment? |
@abonander apologies for the delay. I have pushed an alternative proposal to align with your comments, which is to allow setting the |
…hbadge#3137) * SqliteConnectOptions::filename() memory fix (launchbadge#3136) * Expose in_memory sqlite option * Docs SqliteConnectOptions::filename include mention of from_str alternative * Docs SqliteConnectOptions::filename typo fix
…hbadge#3137) * SqliteConnectOptions::filename() memory fix (launchbadge#3136) * Expose in_memory sqlite option * Docs SqliteConnectOptions::filename include mention of from_str alternative * Docs SqliteConnectOptions::filename typo fix
…hbadge#3137) * SqliteConnectOptions::filename() memory fix (launchbadge#3136) * Expose in_memory sqlite option * Docs SqliteConnectOptions::filename include mention of from_str alternative * Docs SqliteConnectOptions::filename typo fix
Fixes #3136