Bug: 404 on POST /rest/v1/doctors despite table exists, RLS disabled, pgcrypto enabled
RLS🔢DB ConnectionsPostgRESTIssue: Any POST to /rest/v1/doctors returns 404 Not Found + {"code":"42883", "message":"function digest(text, unknown) does not exist"}
What has been confirmed:
- Table "doctors" exists in public schema (visible in Table Editor)
- RLS is DISABLED (relrowsecurity = false via SELECT from pg_class)
- pgcrypto extension enabled successfully
- UNIQUE index on phone column created successfully
- Client code uses pure .insert() (no upsert, no onConflict), followed by .select("id").single()
- tenant_id is set to auth.uid() (user is authenticated, user.id is correct)
- NOTIFY pgrst 'reload schema' and pg_notification_queue_usage() executed
- Project paused and resumed (no change)
Full error in console:
404 Not Found
{code: "42883", message: "function digest(text, unknown) does not exist", hint: "No function matches the given name and argument types. You might need to add explicit type casts."}
Attached screenshots: Table Editor, relrowsecurity query result, full console log.
Looks like PostgREST schema cache is corrupted or reflection bug.
Already opened a ticket in dashboard. Can you check PostgREST logs internally?
Thanks!
What has been confirmed:
- Table "doctors" exists in public schema (visible in Table Editor)
- RLS is DISABLED (relrowsecurity = false via SELECT from pg_class)
- pgcrypto extension enabled successfully
- UNIQUE index on phone column created successfully
- Client code uses pure .insert() (no upsert, no onConflict), followed by .select("id").single()
- tenant_id is set to auth.uid() (user is authenticated, user.id is correct)
- NOTIFY pgrst 'reload schema' and pg_notification_queue_usage() executed
- Project paused and resumed (no change)
Full error in console:
404 Not Found
{code: "42883", message: "function digest(text, unknown) does not exist", hint: "No function matches the given name and argument types. You might need to add explicit type casts."}
Attached screenshots: Table Editor, relrowsecurity query result, full console log.
Looks like PostgREST schema cache is corrupted or reflection bug.
Already opened a ticket in dashboard. Can you check PostgREST logs internally?
Thanks!
