[LogosDB] Bump version to v0.2.0 for delete/update operations
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
Research direction
Start in CMakeLists.txt lines 188-197 and tools/cli/cli.cpp, then compare the documented API in SPECS.md with LogosDB v0.2.0. Verify that the project compiles and links, IDs are retained for new memories, the requested delete/update and statistics commands work, and SPECS.md documents the updated version and API.
Written by the indexing model from the issue text.
Description
Summary
Update LogosDB from v0.1.0 to v0.2.0 to enable memory deletion and updates.
Current State
- CMakeLists.txt pins LogosDB to
GIT_TAG v0.1.0 - Missing delete/update functionality in semantic memory
LogosDB v0.2.0 New Features
logosdb_delete(db, id, &err)- Mark rows as deleted (excluded from search)logosdb_update(db, id, embedding, dim, text, timestamp, &err)- Replace existing rowslogosdb_count_live(db)- Count non-deleted rowslogosdb_result_id(res, i)- Get IDs from search results
Required Changes
- CMakeLists.txt: Bump
GIT_TAGtov0.2.0 - cli.cpp: Store returned IDs from
logosdb_put()for future delete/update - SPECS.md: Update documented version and API
New CLI Commands to Add
/forget <id>or/delete <query>- Remove specific memories/update <id> <new_text>- Replace a memory/listor/count- Show memory statistics (live vs total)
Acceptance Criteria
- CMakeLists.txt updated to v0.2.0
- Code compiles and links with v0.2.0
- Store IDs when teaching new memories
- Add
/deletecommand (by ID or by search) - Add memory stats display
- Update SPECS.md
Related Files
CMakeLists.txt(lines 188-197)tools/cli/cli.cpp(embedding storage, search)SPECS.md
- Dominant language
- C++
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from jose-compu/funes.cpp
-
stale
Difficulty 5/5 Over a week Newbie friendliness 25/100
jose-compu/funes.cpp#12 ·
-
stale
Difficulty 4/5 3-5 days Newbie friendliness 52/100
jose-compu/funes.cpp#11 ·
-
stale
Difficulty 4/5 3-5 days Newbie friendliness 48/100
jose-compu/funes.cpp#10 ·
-
stale
Difficulty 4/5 3-5 days Newbie friendliness 55/100
jose-compu/funes.cpp#9 ·
-
stale
Difficulty 4/5 3-5 days Newbie friendliness 48/100
jose-compu/funes.cpp#7 ·
All issues in jose-compu/funes.cpp
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
sandialabs/seacas#945 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
ROCm/FastFlowLM#757 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
espressif/esp-matter#1867 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
mltframework/shotcut#1920 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day