Repository navigation
node:sqlite support SQLITE_OPEN_URI #57068
Description
Activity
I think it makes sense to always pass
SQLITE_OPEN_URIsince Node.js tries to support URLs and file pathsWould be totally fine by me. I proposed the conservative option mainly because I don't know how much you care about the overlap between URIs and valid filepaths on Linux and BSDs, e.g.
file:///bin/shcould either mean/bin/shor./file:/bin/shon Linux.Reacted by Edy SilvaI think it makes sense to always pass
SQLITE_OPEN_URIsince Node.js tries to support URLs and file paths (related #56940).Great! I took the opportunity to do this flag as default in that PR. It's ready for review
Maybe it's worth to consider the fourth option: Pass
SQLITE_OPEN_URIif and only if the user provided anURLobject forlocation🤔@BurningEnlightenment @cjihrig do you think we can close this issue since now, sqlite is accepting URL as database path and SQLITE_OPEN_URI is enabled?
I think so. Thanks!
Can this be backported to the next
22release?Can this be backported to the next
22release?Yeah, I think so. Let me open it.
Reacted by Henrik Gaßmann
What is the problem this feature will solve?
I have a custom SQLite VFS implementation and I want to open a database within the VFS. SQLite allows me to specify the VFS implementation as a query parameter for URI filenames.
What is the feature you are proposing to solve the problem?
Add an
allowLocationUriboolean property toDatabaseSync#optionswhich causesSQLITE_OPEN_URIto be passed tosqlite3_open_v2().What alternatives have you considered?
SQLITE_OPEN_URItosqlite3_open_v2()likego-sqlite3or the rust bindingsrusqlitedo. Note that specifyingSQLITE_OPEN_URIdoes not requirelocationto be an URI.node-sqlite3chose this path.