Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 9 additions & 9 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,15 +15,15 @@

## Why Use SQLite-Vector?

| Feature | SQLite-Vector | Traditional Solutions |
| -------------------------- | ------------- | ------------------------------------------ |
| Works with ordinary tables | ✅ | ❌ (usually require special virtual tables) |
| Requires preindexing | ❌ | (can take hours for large datasets) |
| Requires external server | ❌ | (often needs Redis/FAISS/Weaviate/etc.) |
| Memory-efficient | ✅ | ❌ |
| Easy to use SQL | ✅ | ❌ (often complex JOINs, subqueries) |
| Offline/Edge ready | ✅ | ❌ |
| Cross-platform | ✅ | ❌ |
| Feature | SQLite-Vector | Traditional Solutions |
| ---------------------------- | ------------- | ------------------------------------------ |
| Works with ordinary tables | ✅ | ❌ (usually require special virtual tables) |
| Doesn't need preindexing | ✅ | (can take hours for large datasets) |
| Doesn't need external server | ✅ | (often needs Redis/FAISS/Weaviate/etc.) |
| Memory-efficient | ✅ | ❌ |
| Easy to use SQL | ✅ | ❌ (often complex JOINs, subqueries) |
| Offline/Edge ready | ✅ | ❌ |
| Cross-platform | ✅ | ❌ |

Unlike other vector databases or extensions that require complex setup, SQLite-Vector **just works** with your existing database schema and tools.

Expand Down