Retrieval Augmented Generation Based on SQLite
1–10 of 13 posts
Re: Retrieval Augmented Generation Based on SQLite
#2Re: Retrieval Augmented Generation Based on SQLite
#3Anyone want to help out?
Re: Retrieval Augmented Generation Based on SQLite
#4This looks cool, and I'm interested in these keywords, but I read the entire readme and I'm still unsure what problem it's actually solving. Anyone want to help out?
Re: Retrieval Augmented Generation Based on SQLite
#5This looks cool, and I'm interested in these keywords, but I read the entire readme and I'm still unsure what problem it's actually solving. Anyone want to help out?
This makes the search less precise and more powerful at the same time (ie it could look clever to some extent).
Re: Retrieval Augmented Generation Based on SQLite
#6Re: Retrieval Augmented Generation Based on SQLite
#7Sqlite has an embedding search? Or is that being provided by this tool?
Re: Retrieval Augmented Generation Based on SQLite
#8Re: Retrieval Augmented Generation Based on SQLite
#9Re: Retrieval Augmented Generation Based on SQLite
#10Would love to see a system that blends cheap lexical (Fulltext Search) or semantic/vector search using SQLite and chooses the best approach given the input.
Having the FTS engine provide a google-style snippet of the most relevant document chunk is the holy grail for RAG applications. Lucene does this kind of thing better than anyone else:
https://lucene.apache.org/core/8_0_0/highlighter/org/apache/...
It is also very easy to customize this engine and align the document tokenization & indexing concerns with your specific retrieval scenarios.