russellromney/honker v0.5.0

Honker 0.5.0

on GitHub

Every binding, published to every registry. This is the first release where the SQLite extension is installable rather than something you build yourself.

Install

Go, C++, and anything else that loads a SQLite extension: download from ext-v0.5.0 — five platform builds with checksums.

Using Honker with an ORM

You no longer have to find the extension yourself. It installs alongside the binding, and each language tells you where it is:

const { extensionPath } = require('@russellthehippo/honker-node/extension');
db.loadExtension(extensionPath());

from honker import extension_path

# config/database.yml
extensions:
  - <%= Honker.extension_path %>

load_extensions: [Honker.Extension.path!()]

HonkerExtension.Locate()

sql.Register("sqlite3_honker", &sqlite3.SQLiteDriver{Extensions: []string{extPath}})

Set HONKER_EXTENSION_PATH to override, which is also how you use Honker on a platform with no prebuilt package.

The ORM guides cover Drizzle, Kysely, better-sqlite3, GORM, sqlx, Ecto, ActiveRecord, Hibernate, jOOQ, Exposed, and Microsoft.Data.Sqlite. CI runs every one of those recipes on each commit.

Fixes

• #101 — integer SQL parameters now accept whole REAL values, so a plain JavaScript number no longer errors
• #102 — the WAL conversion retries instead of failing the open when another process holds the lock
• #96 — SQLite POSIX locks are preserved in the watcher backends
• #100 — every binding can locate the extension (#99)

Compatibility

No breaking changes. Nothing was removed or resignatured; the extension locators are new API. Minor rather than patch because of those additions.

Attached below: Python wheels, Ruby gems, and the .NET package. Everything is on the registries above — these are for offline or pinned installs.