What's not jumping out to me is why you need an LLM for this? What unique code is the LLM actually generating when de-hallucinating? From the looks of it, the

What's not jumping out to me is why you need an LLM for this? What unique code is the LLM actually generating when de-hallucinating? From the looks of it, they're just advertising a SQL extension that adds vectorization and vector search. Further, it looks like the only thing that the LLM is doing here is deciding which column to run the vector search on. Why is that even necessary? Why are you not pre-processing "vector'd" columns into a normalized format to query against? They're basically adding an unnecessary LLM step to what amounts to a vector search. In fact, the LLM is essentially blindly deciding which column is the best column to pull an answer from. ----- EDIT: Just struck me how terrifyingly dangerous this blog is. Really tired of seeing this crap in the LLM community. The basic premise of this blog is "give an LLM complete access to your database. Let it decide how and where it should pull data from". This is basically useless without talking about how you prevent the LLM from pulling data from places you don't want it to. A far better and safer approach remains to push your relevant fields to a separate place for your LLM. In the spirit of this blog, you should just index to a new table. More realistically, you should just put this in a vector store.