docs+flaky test

docs/api/sqlite.md

@@ -417,12 +417,12 @@ db.loadExtension("myext");
 To use the advanced `sqlite3_file_control` API, call `.fileControl(cmd, value)` on your `Database` instance.
 
 ```ts
-import { Database } from "bun:sqlite";
+import { Database, constants } from "bun:sqlite";
 
 const db = new Database();
 // Ensure WAL mode is NOT persistent
 // this prevents wal files from lingering after the database is closed
-db.fileControl(SQL.constants.SQLITE_FCNTL_PERSIST_WAL, 0);
+db.fileControl(constants.SQLITE_FCNTL_PERSIST_WAL, 0);
 ```
 
 `value` can be:

test/js/bun/sqlite/sqlite.test.js

@@ -2,7 +2,7 @@ import { expect, it, describe } from "bun:test";
 import { Database, constants, SQLiteError } from "bun:sqlite";
 import { existsSync, fstat, readdirSync, realpathSync, rmSync, writeFileSync } from "fs";
 import { spawnSync } from "bun";
-import { bunExe, tempDirWithFiles } from "harness";
+import { bunExe, isWindows, tempDirWithFiles } from "harness";
 import { tmpdir } from "os";
 import path from "path";
 
@@ -852,7 +852,10 @@ it("can continue to use existing statements after database has been GC'd", async
  expect(stmt.all()).toEqual([{ id: 1, name: "foo" }]);
  stmt.finalize();
  expect(() => stmt.all()).toThrow();
- expect(called).toBe(true);
+ if (!isWindows) {
+ // on Windows, FinalizationRegistry is more flaky than on POSIX.
+ expect(called).toBe(true);
+ }
 });
 
 it("statements should be disposable", () => {