Question 1

Can TextQL access Supabase auth and storage schema tables?

Accepted Answer

Yes. TextQL discovers tables across all schemas in your Supabase project, including auth.users, auth.sessions, storage.objects, and storage.buckets. Ana uses these tables to answer questions about authentication patterns, user sessions, and file storage — alongside your application's custom tables.

Question 2

Should I use a read replica or the primary database connection?

Accepted Answer

We recommend connecting TextQL to a Supabase read replica for production projects. This ensures analytics queries don't compete with your application's reads and writes. Supabase offers read replicas on Pro plans and above. For development or staging projects, connecting directly to the primary database is fine.

Question 3

How do I get my Supabase connection string?

Accepted Answer

Go to your Supabase project dashboard, navigate to Settings > Database, and copy the connection string under "Direct connection." Paste this into TextQL's setup form. Make sure to use the direct connection (not the pooled connection) for best schema discovery results.

Question 4

Can TextQL handle Supabase row-level security?

Accepted Answer

TextQL connects via a direct Postgres connection, which bypasses Supabase's API-level RLS by default. We recommend creating a dedicated read-only Postgres user with appropriate schema grants to control exactly which tables and columns TextQL can access.

Question 5

Can I query Supabase and my data warehouse together?

Accepted Answer

Yes. TextQL's multi-source query capability lets you join Supabase application data with warehouse data from Snowflake, BigQuery, or other connected sources. For example, ask "compare signup data in Supabase with marketing attribution in BigQuery" and get a unified answer.