PROBLEM: Supabase Vector Store queries the wrong despite correct configuration. The Vector store connects correctly to my Supabase project, and I can chose from the projects 3x tables. I chose the table ‘hkex_ipo_listings’ for the vector store to retrieve its documents from, BUT instead teh vector store retireves the data from the wrong ‘documents’ table.
PARTIAL SOLUTION: In this community I found two posts that addressed the same issue but the posts are closed, so i cant ask follow-ups.
- Strange Supabase Vector Store behavior in n8n: Queries the wrong table despite correct configuration - #2 by Tommy_dr
- N8N Flow not using correct Supabase Table for Rag Flow - #2 by n8n
The posts narrowed down the problem to the Supabase SQL function match_documents which I setup using the default langchain template in Supabase. Meaning, the n8n Vector store matches the request to the ‘documents’ table instead of the ‘hkex_ipo_listings’ table, despite ‘hkex_ipo_listings’ table, being selected in the interface. The suggestion was to include a SQL fucntion ‘match_hkex_ipo_listings’, which i did. However, the n8n SUpabase vector store still queries the ‘documents’ table & now i have two tables in the selector ‘hkex_ipo_listings’ and ‘rpc/hkex_ipo_listings’.
What am I doing wrong? If i am having a basic flawd understanding, feel free to just send me to article or youtube video about Supabase basics. I watched a few already (I am a noob), but apparantely that wasnt enough. Thanks a lot for your help in advance!!
