#moonsqlite

Moved on mooncakes from Lfan-ke/moonsqlite to moonbitstack/moonsqlite.

#Quickstart

The package name is hyphenated, so import it under an alias in moon.pkg.json — {"path": "moonbitstack/moonsqlite", "alias": "sqlite"} — and reach it as @sqlite (as below). Value constructors come from @moondb (moon add moonbitstack/moondb).

// native target only — this package links the vendored amalgamation.
fn demo() -> Unit raise @moondb.DbError {
  let db = @sqlite.SqliteDriver::open(":memory:")   // implements @moondb.Driver
  db.execute("CREATE TABLE users (id INTEGER PRIMARY KEY, name TEXT, age INTEGER)", [])
  |> ignore

  // Bound params map to SQLite storage classes — never spliced into the SQL text.
  db.execute("INSERT INTO users (name, age) VALUES (?, ?)", [
    @moondb.Text("alice"), @moondb.Int(30),
  ]) |> ignore

  // Result columns decode back into @moondb.Value by their runtime type.
  let rows = db.query("SELECT name, age FROM users WHERE age > ?", [@moondb.Int(18)])
  let _ = rows[0].text(0)   // "alice"
  let _ = rows[0].int(1)    // 30
  db.close()
}

#Using it with moonorm

let sess = @moonorm.Session::new(@sqlite.SqliteDriver::open("app.db"))
sess.add(@moonorm.insert("users").set("name", @moondb.Text("bob"))) |> ignore
let rows = sess.fetch(@moonorm.select("users").where_("name", "=", @moondb.Text("bob")))

#Design & boundaries (honest)

• Isolated C. The amalgamation and a thin FFI stub (sqlite/stub.c) live in sqlite/, marked linguist-vendored so GitHub reports this as a MoonBit project. Nothing outside this package touches C.
• Handles are integers. Opaque sqlite3* / sqlite3_stmt* pointers cross the FFI as Int64 (their pointer bits), inert to the GC — the native runtime never reference-counts or frees a foreign pointer.
• Injection-safe to the wire. Values are bound out-of-band by SQLite (sqlite3_bind_*), never interpolated into the SQL string. Text, integers, doubles, blobs, booleans (as 0/1), and NULL all round-trip.
• Real, verified execution. The integration tests open an actual in-memory SQLite database and assert on rows read back across CREATE / INSERT / SELECT / UPDATE / DELETE, transactions, blob round-trips, and error propagation. They are mutation-verified: neutering the C bind path turns them red, so "it runs" is proven, not claimed.

#License