You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Queries hit the `public` schema by default. Target a custom schema by chaining `.schema()` — the table name stays bare (it maps to PostgREST's `Accept-Profile`/`Content-Profile` header):
Or set a default schema for every query when creating the client:
202
+
203
+
```javascript
204
+
constinsforge=createClient({
205
+
baseUrl:"...",
206
+
anonKey:"...",
207
+
db: { schema:"analytics" },
208
+
});
209
+
```
210
+
211
+
The schema must be exposed by the backend, and access is still gated by grants + RLS like `public`. Older backends that don't expose the schema return PostgREST `PGRST106` rather than silently falling back.
0 commit comments