Add tests, schema sync safeguards, and query/handler improvements

- 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]>

README.md

@@ -35,6 +35,7 @@ A schema-driven MariaDB manager for [Bun](https://bun.sh), featuring automatic s
 - [TypeScript Type Generation](#typescript-type-generation)
 - [Default Fields](#default-fields)
 - [Project Structure](#project-structure)
+- [Testing](#testing)
 
 ---
 
@@ -376,9 +377,11 @@ CLI binary: `bun-mariadb`.
 bunx bun-mariadb schema [options]
 ```
 
-| Option            | Description                                             |
-| ----------------- | ------------------------------------------------------- |
-| `-t`, `--typedef` | Also generate TypeScript type definitions after syncing |
+| Option            | Description                                                              |
+| ----------------- | ------------------------------------------------------------------------ |
+| `-t`, `--typedef` | Also generate TypeScript type definitions after syncing                  |
+| `--dry-run`       | Print the planned schema changes without applying them                   |
+| `-y`, `--yes`     | Apply destructive changes (dropped tables / columns) without confirmation |
 
 **Examples:**
 
@@ -388,8 +391,13 @@ bunx bun-mariadb schema
 
 # Sync schema and regenerate types
 bunx bun-mariadb schema --typedef
+
+# Review planned changes first
+bunx bun-mariadb schema --dry-run
 ```
 
+Changes that discard data (dropping a table or column, or recreating a `VECTOR` column whose size changed) are listed and need confirmation before they run. Non-interactive runs (CI, scripts) refuse them unless `--yes` is passed.
+
 What it does:
 
 1. Ensures the internal `__db_schema_manager__` tracking table exists
@@ -665,9 +673,11 @@ await BunMariaDB.delete({
 ### Raw SQL
 
 ```ts
-BunMariaDB.sql<T>({ sql, values? })
+BunMariaDB.sql<T>({ sql, values?, config? })
 ```
 
+`success` reflects whether the query ran; a `SELECT` with no rows returns `success: true` and an empty `payload`.
+
 ```ts
 const res = await BunMariaDB.sql({
     sql: "SELECT * FROM users WHERE id = ?",
@@ -941,8 +951,21 @@ bun-mariadb/
 │       ├── sql-insert-generator.ts
 │       ├── sanitize-html-fields.ts
 │       └── ...
-└── test/
-    └── coderank/                       # Example project
+└── tests/                              # bun test suite
+```
+
+---
+
+## Testing
+
+```bash
+bun run test
+```
+
+Unit tests need no database. The MariaDB integration tests run only when `BUN_MARIADB_TEST_DB` is set (plus the usual `BUN_MARIADB_SERVER_*` variables). Point it at a throwaway database: the tests create and drop tables.
+
+```bash
+BUN_MARIADB_TEST_DB=bun_mariadb_test bun run test
 ```
 
 ---