about summary refs log tree commit diff
path: root/schema.sql
diff options
context:
space:
mode:
authorPjotr Prins <pjotr.public01@thebird.nl>2026-11-16 16:20:48 +0000
committerPjotr Prins <pjotr.public01@thebird.nl>2026-11-16 16:20:48 +0000
commitdc4c16203674191c4821b2f7b53e01febb7a11a6 (patch)
tree06bc8b8dc19e3b1d72b2fb9475a62bf6fb444243 /schema.sql
parent4e3a785e6aec4f8b2eafad82cb35524359751946 (diff)
downloadai-memory-dc4c16203674191c4821b2f7b53e01febb7a11a6.tar.gz
index: title a reasoning doc with its gist, and make --rebuild stand alone
A reasoning document was titled with the subject of the commit it is attached
to (COALESCE(c.subject,'') through a LEFT JOIN), which is wrong twice over: an
entry recorded with --commit none -- every entry before its commit exists --
was indexed with an empty title, and its gist, the assessed one-line claim
that `list` and `why` show, was not indexed as text at all; an attached entry
merely repeated the title its commit document already carries. The title is
now the entry's own gist, from reasoning.gist, and the join is gone.

`update-index --rebuild` also died with "mkdir failed (No such file or
directory)" whenever the index directory was absent -- the state of every
store that has never been indexed, and the state README.md tells a reader to
produce by deleting the index. Only the non-rebuild path created the
directory; `mkdir -p` now runs before the database handle either way.

The check phase records a gist deliberately different from the body and
asserts both that it answers a search and that it is the document's title, so
a regression fails the build rather than the reader.

.gitignore covers *.sqlite.d/, the default index directory, which neither
*.sqlite nor *.sqlite-* matched -- the README already claimed the index was
ignored.

doc/SKILL.md says what `title` means in a search reply: the gist for a
reasoning entry, the subject for a commit.
Diffstat (limited to 'schema.sql')
0 files changed, 0 insertions, 0 deletions