Skip to content

fix: Let configured file storage reach SQLite on WASI #6

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.

Sign up for GitHub

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

Merged
krodak merged 1 commit into from
Sep 4, 2026
Merged

fix: Let configured file storage reach SQLite on WASI #6

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 13 additions & 3 deletions Sources/SQLiteKit/SQLiteConnectionSource.swift
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,9 +30,19 @@ public struct SQLiteConnectionSource: ConnectionPoolSource, Sendable {

private var connectionStorage: SQLiteConnection.Storage {
#if os(WASI)
// NOTE: For WASI platforms, file urls and paths cause runtime errors currently. Using
// in-memory connection only as a workaround.
.memory
// On WASI, pass the configured storage through directly:
// - `.file` works (sqlite over a preopened directory); pass the raw
// configured path rather than routing through `urlForSQLite`.
// - `.memory` stays a true in-memory database. The temp-file emulation
// of shared in-memory databases (see `urlForSQLite` below) requires a
// usable temporary directory, which WASI hosts do not generally
// preopen.
switch self.configuration.storage {
case .memory:
.memory
case .file(let path):
.file(path: path)
}
#else
.file(path: self.actualURL.absoluteString)
#endif
Expand Down