tursodatabase/turso · error · SqliteException

1

1

Error message

SQLite Error {errorCode}: 'no such vfs: {vfs}'.

What it means

Thrown while normalizing the connection string when the 'Vfs' keyword is non-empty but not one of the two VFS names this managed binding accepts: 'win32-longpath' or 'unix-dotfile' (see IsSupportedVfs in SqliteConnection.cs:789). The message mirrors SQLite's native 'no such vfs' error with SQLite error code 1 (SQLITE_ERROR). Unlike Microsoft.Data.Sqlite, which forwards the name to the native library where many VFS modules exist, this binding validates the name itself and fails before any database is opened.

Source

Thrown at bindings/dotnet/src/Turso.Data.Sqlite/SqliteConnection.cs:733

        return true;
    }

    private static void SkipSqlWhitespace(string sql, ref int index)
    {
        while (index < sql.Length && char.IsWhiteSpace(sql[index]))
            index++;
    }

    private static bool IsSqlIdentifierPart(char value)
        => char.IsLetterOrDigit(value) || value == '_' || value == '$';

    private static string NormalizeDataSource(SqliteConnectionStringBuilder options)
    {
        var dataSource = options.DataSource;
        if (string.IsNullOrEmpty(dataSource))
            return ":memory:";
        if (options.Vfs is { Length: > 0 } vfs && !IsSupportedVfs(vfs))
            throw new SqliteException(Properties.Resources.SqliteNativeError(SQLITE_ERROR, "no such vfs: " + vfs), SQLITE_ERROR);
        if (dataSource == ":memory:")
            return dataSource;
        if (options.Mode == SqliteOpenMode.Memory)
            return options.Cache == SqliteCacheMode.Shared && dataSource.Length > 0
                ? GetSharedMemoryFile(dataSource)
                : ":memory:";
        if (dataSource.StartsWith("file:", StringComparison.OrdinalIgnoreCase))
            return NormalizeUriDataSource(dataSource);

        const string dataDirectory = "|DataDirectory|";
        if (dataSource.StartsWith(dataDirectory, StringComparison.OrdinalIgnoreCase))
        {
            var baseDirectory = AppDomain.CurrentDomain.GetData("DataDirectory") as string
                                ?? AppContext.BaseDirectory;
            dataSource = Path.Combine(baseDirectory, dataSource[dataDirectory.Length..].TrimStart(Path.DirectorySeparatorChar, Path.AltDirectorySeparatorChar));
        }

        var filename = Path.IsPathRooted(dataSource)

View on GitHub (pinned to 244cde92a7)

Solutions

1. Remove the 'Vfs=' entry from the connection string; it is optional and the binding uses its own virtual file system.
2. If you need the behavior it provided, use one of the two accepted values: Vfs=win32-longpath (Windows long paths) or Vfs=unix-dotfile (dot-file locking).
3. Search your config files, appsettings, and ORM setup (e.g. UseSqlite("...")) for 'Vfs=' and delete or correct every occurrence.

Example fix

// before
var conn = new SqliteConnection("Data Source=app.db;Vfs=unix-excl");

// after
var conn = new SqliteConnection("Data Source=app.db");
// or, if dot-file locking is specifically wanted:
var conn = new SqliteConnection("Data Source=app.db;Vfs=unix-dotfile");

static readonly string[] SupportedVfs = { "win32-longpath", "unix-dotfile" };
static bool VfsOk(string? vfs)
    => string.IsNullOrEmpty(vfs)
    || SupportedVfs.Contains(vfs, StringComparer.OrdinalIgnoreCase);

if (!VfsOk(config.Vfs)) throw new ConfigException($"Unsupported Vfs '{config.Vfs}'.");

try { conn.Open(); }
catch (SqliteException ex) when (ex.SqliteErrorCode == 1 && ex.Message.Contains("no such vfs"))
{ /* strip Vfs from the connection string and rebuild */ }

When it happens

Trigger: Constructing SqliteConnection with a connection string containing 'Vfs=unix-excl' (or 'unix', 'win32', 'unix-none'), or setting builder.Vfs = "unix-excl". Anything except 'win32-longpath' and 'unix-dotfile' (case-insensitive) throws from NormalizeDataSource.

Common situations: Copying a connection string written for Microsoft.Data.Sqlite or System.Data.SQLite whose bundled native SQLite supports more VFS names; attempting long-path or dot-file locking workarounds copied from SQLite docs; migrating an app to the Turso managed binding without pruning unsupported options.

Related errors

• 14
• Keyword not supported: {keyword}.
• Invalid value {value} for enum type {enumType}.
• Cannot convert {sourceType} to {targetType}.
• The data is NULL at ordinal {ordinal}.

AI-assisted analysis of tursodatabase/turso@244cde92a7 (2026-08-20). Data as JSON: /api/errors/d5fdeffdf5164900. Report an issue: GitHub.