dirsql 0.4.68__tar.gz → 0.4.69__tar.gz

{dirsql-0.4.68 → dirsql-0.4.69}/Cargo.lock

@@ -552,7 +552,7 @@ checksum = "6184e33543162437515c2e2b48714794e37845ec9851711914eec9d308f6ebe8"
 
 [[package]]
 name = "dirsql"
-version = "0.4.68"
+version = "0.4.69"
 dependencies = [
  "assert_cmd",
  "axum",
@@ -574,6 +574,7 @@ dependencies = [
  "notify",
  "predicates",
  "reedline",
+ "regex",
  "reqwest",
  "rusqlite",
  "serde",
@@ -600,7 +601,7 @@ dependencies = [
 
 [[package]]
 name = "dirsql-py-ext"
-version = "0.4.68"
+version = "0.4.69"
 dependencies = [
  "dirsql",
  "pyo3",

{dirsql-0.4.68 → dirsql-0.4.69}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: dirsql
-Version: 0.4.68
+Version: 0.4.69
 Requires-Dist: bin-shim>=0.1
 Summary: Ephemeral SQL index over a local directory
 Keywords: sql,filesystem,directory,sqlite,index

{dirsql-0.4.68/packages/rust → dirsql-0.4.69}/docs/context/troubleshooting.md

@@ -45,7 +45,7 @@ uvx dirsql "SELECT path FROM './**'" --format json
 ### Empty `[]` for files you can see
 
 - **You named a directory**, which lists one level only. `'./**'` and `'./docs/**'` are the recursive forms.
-- **The files are gitignored.** `--no-ignore` scans them:
+- **The files are gitignored**, inside a git repo (outside one, no `.gitignore` applies). `--no-ignore` scans them:
 
   ```sh
   uvx dirsql "SELECT path FROM './**'" --format json --no-ignore

{dirsql-0.4.68/packages/rust → dirsql-0.4.69}/docs/context/usage.md

@@ -35,7 +35,7 @@ Every row has `path`, `basename`, `dir`, `ext` (no dot, `NULL` when absent), `si
 
 ### What a scan skips
 
-- **`.gitignore` is respected.** Pass `--no-ignore` to scan gitignored files too, or name the ignored directory outright: `'./build'` scans `build/`.
+- **`.gitignore` is respected inside a git repo**, as git does; outside one (no enclosing `.git`) no `.gitignore` applies. Pass `--no-ignore` to scan gitignored files too, or name the ignored directory outright: `'./build'` scans `build/`.
 - **`node_modules` is skipped** unless the path names it: `'./node_modules/**'`.
 - **`'./**'` does not enter `.git`.** Naming it scans it: `'./.git/**'`.
 - **To match dotfiles, spell the dot:** `'./.github/**'`, `'./**/.env'`.

{dirsql-0.4.68 → dirsql-0.4.69}/docs/reference/cli.md

@@ -278,7 +278,7 @@ with all seven [stat columns](./columns.md): `path`, `basename`, `dir`, `ext`,
 
 ```bash
 curl -s localhost:7117/query -H 'content-type: application/json' \
-  -d '{"sql":"SELECT basename, size FROM \'./\' ORDER BY size DESC LIMIT 5"}'
+  -d "{\"sql\":\"SELECT basename, size FROM './' ORDER BY size DESC LIMIT 5\"}"
 ```
 
 Earlier versions served an implicit table named `files` here. It is gone; a

{dirsql-0.4.68 → dirsql-0.4.69}/docs/reference/http-api.md

@@ -27,7 +27,7 @@ The `200` response is a JSON array of row objects keyed by column name:
 ```bash
 curl -s http://localhost:7117/query \
   -H 'content-type: application/json' \
-  -d '{"sql":"SELECT COUNT(*) AS n FROM \'./\'"}' \
+  -d "{\"sql\":\"SELECT COUNT(*) AS n FROM './'\"}" \
   | jq
 ```
 

{dirsql-0.4.68/packages/python → dirsql-0.4.69}/docs/reference/path-tables.md

@@ -55,9 +55,10 @@ A path containing `*`, `?`, `[` or `{` is a glob and is used exactly as
 written: `*` matches within a single directory, `**` crosses directories.
 
 The scan starts at the last directory named outright before the first glob
-component -- `'./small/*.md'` walks `small/` and nothing else -- so a query
-over one directory costs what `find ./small` costs, however large the
-directories beside it.
+component, and descends only as deep as the pattern can match --
+`'./small/*.md'` lists `small/` and nothing else -- so a query over one
+directory costs what `ls small` costs, however large the directories beside
+or below it. Only `**` walks a whole subtree.
 
 A path naming a single file yields exactly one row. dirsql never splits a file
 into rows on its own — that is what a table's `on_file` hook is for.
@@ -260,15 +261,21 @@ skipped just like one at the top.
 
 ### `.gitignore`
 
-Path-table scans also respect `.gitignore` files by default, the way fd and
-ripgrep do: a `.gitignore` anywhere in the tree applies below its own
+Path-table scans also respect `.gitignore` files by default, inside a git
+repo, the way git, fd and ripgrep do: a `.gitignore` applies below its own
 directory, deeper files override shallower ones, `!pattern` re-includes, and
 an ignored directory is pruned rather than walked. In a typical repo this
-excludes build output, virtualenvs, and caches with zero ceremony. No `.git`
-directory is required — a `.gitignore` in any scanned directory counts — and
-the built-in defaults above remain as a floor for directories with no
+excludes build output, virtualenvs, and caches with zero ceremony. The
+built-in defaults above remain as a floor for directories with no
 `.gitignore` at all.
 
+A `.gitignore` is in force only when a directory holding `.git` encloses it.
+Outside a repo none applies, at the scan's start, above it or below it: a
+`~/.claude` whose `.gitignore` is `*` still lists its files when `~/.claude`
+is not a repo. Inside one, every `.gitignore` from the repo root down
+applies, including those above the directory a scan starts in, so
+`'./docs/*.log'` and `'./**/*.log'` agree about `docs/`.
+
 Pass [`--no-ignore`](./cli.md#flags) to restore the full walk — the
 determinism switch for scripted use, since results otherwise depend on
 `.gitignore` state. It disables only the `.gitignore` respect; the built-in
@@ -285,8 +292,8 @@ SELECT path FROM './node_modules/*/package.json';  -- scans it anyway
 SELECT path FROM './dist';                 -- scans dist/ even when gitignored
 ```
 
-A `.gitignore` at or below the directory the scan starts in still filters
-beneath it; one above it is never read.
+The `.gitignore` files in force there, including those above it, still
+filter what lies beneath it.
 
 ### Hidden files
 

{dirsql-0.4.68 → dirsql-0.4.69}/packages/python/Cargo.toml

@@ -4,7 +4,7 @@ name = "dirsql-py-ext"
 # pypi/maturin handler can rewrite it via `write-version` before
 # `maturin build`. `pyproject.toml` declares `dynamic = ["version"]`
 # and maturin reads this field. Mirrors `packages/rust/Cargo.toml`.
-version = "0.4.68"
+version = "0.4.69"
 # abi3 note: the `abi3-py310` pyo3 feature (below) builds ONE stable-ABI
 # `cp310-abi3` wheel per platform that loads on every CPython >= 3.10
 # (matching `pyproject.toml`'s `requires-python = ">=3.10"`), instead of

dirsql-0.4.69/packages/python/changelog.d/2026-10-05-gitignore-requires-repo.md

@@ -0,0 +1,5 @@
+**Changed** A `.gitignore` applies to path-table scans only inside a git
+repo, as in git, fd and ripgrep: one is in force only when a directory
+holding `.git` encloses it. Outside a repo none applies, at the scan's start,
+above it or below it, so a `~/.claude` whose `.gitignore` is `*` lists its
+files. Inside a repo nothing changes. `--no-ignore` is unchanged.

{dirsql-0.4.68 → dirsql-0.4.69/packages/python}/docs/context/troubleshooting.md

@@ -45,7 +45,7 @@ uvx dirsql "SELECT path FROM './**'" --format json
 ### Empty `[]` for files you can see
 
 - **You named a directory**, which lists one level only. `'./**'` and `'./docs/**'` are the recursive forms.
-- **The files are gitignored.** `--no-ignore` scans them:
+- **The files are gitignored**, inside a git repo (outside one, no `.gitignore` applies). `--no-ignore` scans them:
 
   ```sh
   uvx dirsql "SELECT path FROM './**'" --format json --no-ignore

{dirsql-0.4.68 → dirsql-0.4.69/packages/python}/docs/context/usage.md

@@ -35,7 +35,7 @@ Every row has `path`, `basename`, `dir`, `ext` (no dot, `NULL` when absent), `si
 
 ### What a scan skips
 
-- **`.gitignore` is respected.** Pass `--no-ignore` to scan gitignored files too, or name the ignored directory outright: `'./build'` scans `build/`.
+- **`.gitignore` is respected inside a git repo**, as git does; outside one (no enclosing `.git`) no `.gitignore` applies. Pass `--no-ignore` to scan gitignored files too, or name the ignored directory outright: `'./build'` scans `build/`.
 - **`node_modules` is skipped** unless the path names it: `'./node_modules/**'`.
 - **`'./**'` does not enter `.git`.** Naming it scans it: `'./.git/**'`.
 - **To match dotfiles, spell the dot:** `'./.github/**'`, `'./**/.env'`.

{dirsql-0.4.68/packages/rust → dirsql-0.4.69/packages/python}/docs/reference/cli.md

@@ -278,7 +278,7 @@ with all seven [stat columns](./columns.md): `path`, `basename`, `dir`, `ext`,
 
 ```bash
 curl -s localhost:7117/query -H 'content-type: application/json' \
-  -d '{"sql":"SELECT basename, size FROM \'./\' ORDER BY size DESC LIMIT 5"}'
+  -d "{\"sql\":\"SELECT basename, size FROM './' ORDER BY size DESC LIMIT 5\"}"
 ```
 
 Earlier versions served an implicit table named `files` here. It is gone; a

{dirsql-0.4.68/packages/rust → dirsql-0.4.69/packages/python}/docs/reference/http-api.md

@@ -27,7 +27,7 @@ The `200` response is a JSON array of row objects keyed by column name:
 ```bash
 curl -s http://localhost:7117/query \
   -H 'content-type: application/json' \
-  -d '{"sql":"SELECT COUNT(*) AS n FROM \'./\'"}' \
+  -d "{\"sql\":\"SELECT COUNT(*) AS n FROM './'\"}" \
   | jq
 ```
 

{dirsql-0.4.68 → dirsql-0.4.69/packages/python}/docs/reference/path-tables.md

@@ -55,9 +55,10 @@ A path containing `*`, `?`, `[` or `{` is a glob and is used exactly as
 written: `*` matches within a single directory, `**` crosses directories.
 
 The scan starts at the last directory named outright before the first glob
-component -- `'./small/*.md'` walks `small/` and nothing else -- so a query
-over one directory costs what `find ./small` costs, however large the
-directories beside it.
+component, and descends only as deep as the pattern can match --
+`'./small/*.md'` lists `small/` and nothing else -- so a query over one
+directory costs what `ls small` costs, however large the directories beside
+or below it. Only `**` walks a whole subtree.
 
 A path naming a single file yields exactly one row. dirsql never splits a file
 into rows on its own — that is what a table's `on_file` hook is for.
@@ -260,15 +261,21 @@ skipped just like one at the top.
 
 ### `.gitignore`
 
-Path-table scans also respect `.gitignore` files by default, the way fd and
-ripgrep do: a `.gitignore` anywhere in the tree applies below its own
+Path-table scans also respect `.gitignore` files by default, inside a git
+repo, the way git, fd and ripgrep do: a `.gitignore` applies below its own
 directory, deeper files override shallower ones, `!pattern` re-includes, and
 an ignored directory is pruned rather than walked. In a typical repo this
-excludes build output, virtualenvs, and caches with zero ceremony. No `.git`
-directory is required — a `.gitignore` in any scanned directory counts — and
-the built-in defaults above remain as a floor for directories with no
+excludes build output, virtualenvs, and caches with zero ceremony. The
+built-in defaults above remain as a floor for directories with no
 `.gitignore` at all.
 
+A `.gitignore` is in force only when a directory holding `.git` encloses it.
+Outside a repo none applies, at the scan's start, above it or below it: a
+`~/.claude` whose `.gitignore` is `*` still lists its files when `~/.claude`
+is not a repo. Inside one, every `.gitignore` from the repo root down
+applies, including those above the directory a scan starts in, so
+`'./docs/*.log'` and `'./**/*.log'` agree about `docs/`.
+
 Pass [`--no-ignore`](./cli.md#flags) to restore the full walk — the
 determinism switch for scripted use, since results otherwise depend on
 `.gitignore` state. It disables only the `.gitignore` respect; the built-in
@@ -285,8 +292,8 @@ SELECT path FROM './node_modules/*/package.json';  -- scans it anyway
 SELECT path FROM './dist';                 -- scans dist/ even when gitignored
 ```
 
-A `.gitignore` at or below the directory the scan starts in still filters
-beneath it; one above it is never read.
+The `.gitignore` files in force there, including those above it, still
+filter what lies beneath it.
 
 ### Hidden files
 

dirsql-0.4.69/packages/python/e2e-attestations/claude-1269-utf8-chars.json

@@ -0,0 +1,7 @@
+{
+  "command": "just test-e2e",
+  "ran_at": 1791215881,
+  "exit_code": 0,
+  "commit": "e6e8716ac1fca13d6b03e48c7ff0551b48c7f537",
+  "branch": "claude/1269-utf8-chars"
+}

dirsql-0.4.69/packages/python/e2e-attestations/claude-1272-ancestor-gitignore.json

@@ -0,0 +1,7 @@
+{
+  "command": "just test-e2e",
+  "ran_at": 1791218987,
+  "exit_code": 0,
+  "commit": "a433cc9c0cf5c32e3d731625dd63ecd040d9f235",
+  "branch": "claude/1272-ancestor-gitignore"
+}

dirsql-0.4.69/packages/python/e2e-attestations/claude-1273-walk-prune.json

@@ -0,0 +1,7 @@
+{
+  "command": "just test-e2e",
+  "ran_at": 1791208404,
+  "exit_code": 0,
+  "commit": "e6dcbe0770d2d87d3a26d6318a4b1f716a677197",
+  "branch": "claude/1273-walk-prune"
+}

dirsql-0.4.69/packages/python/e2e-attestations/claude-1285-ingest-fast.json

@@ -0,0 +1,7 @@
+{
+  "command": "just test-e2e",
+  "ran_at": 1791218826,
+  "exit_code": 0,
+  "commit": "c31adf5c4c57cf7683aed2dddf847f1719d44016",
+  "branch": "claude/1285-ingest-fast"
+}

dirsql-0.4.69/packages/python/migrations.d/2026-10-05-gitignore-requires-repo.md

@@ -0,0 +1,36 @@
+### Python SDK: `.gitignore` applies only inside a git repo
+
+#### Summary
+
+Path-tables used to apply `.gitignore` files with no git repo present. Now a
+`.gitignore` is in force only when a directory holding `.git` encloses it,
+as in git, fd and ripgrep. Every surface that resolves a path-table is
+affected: the CLI, the REPL, the HTTP server, the SDKs, and the `--on-file`
+form. No call changes. Outside a repo a query can return more rows; inside
+one nothing changes.
+
+#### Required changes
+
+_None._
+
+#### Deprecations removed
+
+_None._
+
+#### Behavior changes without code changes
+
+- Outside a git repo, files a `.gitignore` names are listed. To hide them,
+  add `ignore` patterns in a config file, or run `git init`.
+
+#### Verification
+
+```bash
+cd "$(mktemp -d)"
+printf '*.log\n' > .gitignore
+touch a.md z.log
+dirsql query "SELECT path FROM './*' ORDER BY path"
+# expected: [{"path":"a.md"},{"path":"z.log"}]
+git init -q
+dirsql query "SELECT path FROM './*' ORDER BY path"
+# expected: [{"path":"a.md"}]
+```

{dirsql-0.4.68 → dirsql-0.4.69}/packages/rust/Cargo.toml

@@ -6,7 +6,7 @@ description = "Ephemeral SQL index over a local directory"
 # version stays for the binding crates (publish = false). The literal
 # intentionally lags the published version: putitoutthere rewrites it to
 # the planned release version at build time and never commits it back.
-version = "0.4.68"
+version = "0.4.69"
 edition.workspace = true
 # Literal `license` (not `license.workspace = true`) because
 # putitoutthere's preflight check reads `[package].license` directly
@@ -73,6 +73,7 @@ hex = { version = "0.4", optional = true }
 ignore = "0.4"
 indicatif = "0.18.6"
 notify = "7"
+regex.workspace = true
 # The REPL's interactive line editor (history, Ctrl+R, multi-line entry).
 # CLI-only: a library consumer never pulls crossterm.
 reedline = { version = "0.49", optional = true }

{dirsql-0.4.68/packages/python → dirsql-0.4.69/packages/rust}/docs/context/troubleshooting.md

@@ -45,7 +45,7 @@ uvx dirsql "SELECT path FROM './**'" --format json
 ### Empty `[]` for files you can see
 
 - **You named a directory**, which lists one level only. `'./**'` and `'./docs/**'` are the recursive forms.
-- **The files are gitignored.** `--no-ignore` scans them:
+- **The files are gitignored**, inside a git repo (outside one, no `.gitignore` applies). `--no-ignore` scans them:
 
   ```sh
   uvx dirsql "SELECT path FROM './**'" --format json --no-ignore

{dirsql-0.4.68/packages/python → dirsql-0.4.69/packages/rust}/docs/context/usage.md

@@ -35,7 +35,7 @@ Every row has `path`, `basename`, `dir`, `ext` (no dot, `NULL` when absent), `si
 
 ### What a scan skips
 
-- **`.gitignore` is respected.** Pass `--no-ignore` to scan gitignored files too, or name the ignored directory outright: `'./build'` scans `build/`.
+- **`.gitignore` is respected inside a git repo**, as git does; outside one (no enclosing `.git`) no `.gitignore` applies. Pass `--no-ignore` to scan gitignored files too, or name the ignored directory outright: `'./build'` scans `build/`.
 - **`node_modules` is skipped** unless the path names it: `'./node_modules/**'`.
 - **`'./**'` does not enter `.git`.** Naming it scans it: `'./.git/**'`.
 - **To match dotfiles, spell the dot:** `'./.github/**'`, `'./**/.env'`.

{dirsql-0.4.68/packages/python → dirsql-0.4.69/packages/rust}/docs/reference/cli.md

@@ -278,7 +278,7 @@ with all seven [stat columns](./columns.md): `path`, `basename`, `dir`, `ext`,
 
 ```bash
 curl -s localhost:7117/query -H 'content-type: application/json' \
-  -d '{"sql":"SELECT basename, size FROM \'./\' ORDER BY size DESC LIMIT 5"}'
+  -d "{\"sql\":\"SELECT basename, size FROM './' ORDER BY size DESC LIMIT 5\"}"
 ```
 
 Earlier versions served an implicit table named `files` here. It is gone; a

{dirsql-0.4.68/packages/python → dirsql-0.4.69/packages/rust}/docs/reference/http-api.md

@@ -27,7 +27,7 @@ The `200` response is a JSON array of row objects keyed by column name:
 ```bash
 curl -s http://localhost:7117/query \
   -H 'content-type: application/json' \
-  -d '{"sql":"SELECT COUNT(*) AS n FROM \'./\'"}' \
+  -d "{\"sql\":\"SELECT COUNT(*) AS n FROM './'\"}" \
   | jq
 ```
 

{dirsql-0.4.68 → dirsql-0.4.69}/packages/rust/docs/reference/path-tables.md

@@ -55,9 +55,10 @@ A path containing `*`, `?`, `[` or `{` is a glob and is used exactly as
 written: `*` matches within a single directory, `**` crosses directories.
 
 The scan starts at the last directory named outright before the first glob
-component -- `'./small/*.md'` walks `small/` and nothing else -- so a query
-over one directory costs what `find ./small` costs, however large the
-directories beside it.
+component, and descends only as deep as the pattern can match --
+`'./small/*.md'` lists `small/` and nothing else -- so a query over one
+directory costs what `ls small` costs, however large the directories beside
+or below it. Only `**` walks a whole subtree.
 
 A path naming a single file yields exactly one row. dirsql never splits a file
 into rows on its own — that is what a table's `on_file` hook is for.
@@ -260,15 +261,21 @@ skipped just like one at the top.
 
 ### `.gitignore`
 
-Path-table scans also respect `.gitignore` files by default, the way fd and
-ripgrep do: a `.gitignore` anywhere in the tree applies below its own
+Path-table scans also respect `.gitignore` files by default, inside a git
+repo, the way git, fd and ripgrep do: a `.gitignore` applies below its own
 directory, deeper files override shallower ones, `!pattern` re-includes, and
 an ignored directory is pruned rather than walked. In a typical repo this
-excludes build output, virtualenvs, and caches with zero ceremony. No `.git`
-directory is required — a `.gitignore` in any scanned directory counts — and
-the built-in defaults above remain as a floor for directories with no
+excludes build output, virtualenvs, and caches with zero ceremony. The
+built-in defaults above remain as a floor for directories with no
 `.gitignore` at all.
 
+A `.gitignore` is in force only when a directory holding `.git` encloses it.
+Outside a repo none applies, at the scan's start, above it or below it: a
+`~/.claude` whose `.gitignore` is `*` still lists its files when `~/.claude`
+is not a repo. Inside one, every `.gitignore` from the repo root down
+applies, including those above the directory a scan starts in, so
+`'./docs/*.log'` and `'./**/*.log'` agree about `docs/`.
+
 Pass [`--no-ignore`](./cli.md#flags) to restore the full walk — the
 determinism switch for scripted use, since results otherwise depend on
 `.gitignore` state. It disables only the `.gitignore` respect; the built-in
@@ -285,8 +292,8 @@ SELECT path FROM './node_modules/*/package.json';  -- scans it anyway
 SELECT path FROM './dist';                 -- scans dist/ even when gitignored
 ```
 
-A `.gitignore` at or below the directory the scan starts in still filters
-beneath it; one above it is never read.
+The `.gitignore` files in force there, including those above it, still
+filter what lies beneath it.
 
 ### Hidden files
 

{dirsql-0.4.68 → dirsql-0.4.69}/packages/rust/src/db.rs

@@ -1,4 +1,5 @@
 use rusqlite::Connection;
+use rusqlite::types::{ToSql, ToSqlOutput, ValueRef};
 use std::collections::{HashMap, HashSet};
 use std::path::{Path, PathBuf};
 use std::sync::Arc;
@@ -1191,24 +1192,14 @@ pub enum Value {
     Blob(Vec<u8>),
 }
 
-impl rusqlite::types::ToSql for Value {
-    fn to_sql(&self) -> rusqlite::Result<rusqlite::types::ToSqlOutput<'_>> {
+impl ToSql for Value {
+    fn to_sql(&self) -> rusqlite::Result<ToSqlOutput<'_>> {
         match self {
-            Value::Null => Ok(rusqlite::types::ToSqlOutput::Owned(
-                rusqlite::types::Value::Null,
-            )),
-            Value::Integer(i) => Ok(rusqlite::types::ToSqlOutput::Owned(
-                rusqlite::types::Value::Integer(*i),
-            )),
-            Value::Real(f) => Ok(rusqlite::types::ToSqlOutput::Owned(
-                rusqlite::types::Value::Real(*f),
-            )),
-            Value::Text(s) => Ok(rusqlite::types::ToSqlOutput::Owned(
-                rusqlite::types::Value::Text(s.clone()),
-            )),
-            Value::Blob(b) => Ok(rusqlite::types::ToSqlOutput::Owned(
-                rusqlite::types::Value::Blob(b.clone()),
-            )),
+            Value::Null => Ok(ToSqlOutput::Owned(rusqlite::types::Value::Null)),
+            Value::Integer(i) => Ok(ToSqlOutput::Owned(rusqlite::types::Value::Integer(*i))),
+            Value::Real(f) => Ok(ToSqlOutput::Owned(rusqlite::types::Value::Real(*f))),
+            Value::Text(s) => Ok(ToSqlOutput::Borrowed(ValueRef::Text(s.as_bytes()))),
+            Value::Blob(b) => Ok(ToSqlOutput::Borrowed(ValueRef::Blob(b))),
         }
     }
 }
@@ -1283,6 +1274,20 @@ impl From<rusqlite::types::Value> for Value {
 mod tests {
     use super::*;
 
+    #[test]
+    fn text_and_blob_values_bind_without_copying() {
+        let text = Value::Text("abc".into());
+        let blob = Value::Blob(vec![1, 2]);
+        assert_eq!(
+            text.to_sql().unwrap(),
+            ToSqlOutput::Borrowed(ValueRef::Text(b"abc"))
+        );
+        assert_eq!(
+            blob.to_sql().unwrap(),
+            ToSqlOutput::Borrowed(ValueRef::Blob(&[1, 2]))
+        );
+    }
+
     #[test]
     fn create_table_from_ddl() {
         let db = Db::new().unwrap();