An idle Bun.SQL connection does not keep the event loop alive. After an
inquirer prompt released stdin, the next query let Bun exit with code 0
mid-query: `schema` never applied confirmed destructive changes, and
`admin` table views exited instead of showing results. Hold the loop open
for the duration of every query and transaction.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
- Add scripts/test.ts: starts a temporary MariaDB container on a random
localhost port, waits for TCP readiness, runs all test files, and
always removes the container (including on Ctrl+C)
- `bun run test` uses the script; `bun run test:unit` runs without a DB
- BUN_MARIADB_TEST_IMAGE selects the image; an existing
BUN_MARIADB_TEST_DB skips Docker
- Document in README
Co-Authored-By: Claude Opus 5.5 <[email protected]>
- Add bun test suite: SQL generator and value unit tests, plus MariaDB
integration tests gated on BUN_MARIADB_TEST_DB
- schema: add --dry-run and require confirmation (or --yes) before
dropping tables/columns; block unapproved destructive statements
- Always AND targetId with the query, regardless of searchOperator
- Initialize lazily on first call; init throws instead of exiting
- Generate IN (?, ?, ...) lists for IN / NOT IN
- Share value binding between insert and update (booleans, embeddings,
function values, "" -> NULL for non-text columns)
- Keep Buffers and convert BigInt/Date without a JSON round-trip
- DbSQL: report success for empty SELECT results
- Run update() in a transaction with row locking
- Key the client cache on the full connection config
- Consolidate identifier quoting, drop dead code, merge column lookup
- Read CLI version from package.json, pin @types/bun, chmod CLI on compile
- Rebuild dist
Co-Authored-By: Claude Opus 5.5 <[email protected]>
tbenandClaude Opus 5.5