My Supabase RAG Revelation · AI Automation Society

My Supabase RAG Revelation

(this can save you time)

I just discovered a gotcha with Supabase’s VectorStore: no matter which table you pick in the UI, it always hits the “Documents” table you created via the Supabase Docs SQL snippet.

My client has two separate business types, but I use the same Supabase project for both. So the newly created chatbot was querying the wrong database.

Turns out Supabase VectorStore defaults to “Documents” every time—which is fine if you only have one table, but a recipe for confusion when you spin up a second bot inside the same project.

The fix is simple: open your VectorStore settings, click the query name, and change the table reference from “Documents” to your actual table. It exists by default. Do that once and you’ll avoid pulling answers from yesterday’s bot.

Hope this saves you the same headache.

P.S.: To create a table with a different you'll need to alter the SQL query a bit.

8 comments