Skip to content

The Postgres development platform. Supabase gives you a dedicated Postgres database to build your web, mobile, and AI applications.

docs: Add missing MDX extension to troubleshhoting guides (#45091)

Chris Chinchillaf49fcda15c29
diff --git a/apps/docs/content/troubleshooting/postgrest-not-recognizing-objects-in-schema b/apps/docs/content/troubleshooting/postgrest-not-recognizing-objects-in-schema.mdx
similarity index 68%
rename from apps/docs/content/troubleshooting/postgrest-not-recognizing-objects-in-schema
rename to apps/docs/content/troubleshooting/postgrest-not-recognizing-objects-in-schema.mdx
index fa5a15efd65..86feb98ab68 100644
--- a/apps/docs/content/troubleshooting/postgrest-not-recognizing-objects-in-schema
+++ b/apps/docs/content/troubleshooting/postgrest-not-recognizing-objects-in-schema.mdx
@@ -1,9 +1,9 @@
---
title = "PostgREST not recognizing the objects(tables/functions/views) in a schema even after adding it to the exposed schemas"
topics = [
- "database",
- "rest-api",
- "platform"
+"database",
+"rest-api",
+"platform"
]
keywords = []
---
@@ -16,10 +16,10 @@ Could not find the table 'X' in the schema cache
## Why this happens
-When multiple schemas are exposed, the first entry in the list is treated as the default, so PostgREST resolves unqualified object names only against that schema.
+When multiple schemas are exposed, the first entry in the list is treated as the default, so PostgREST resolves unqualified object names only against that schema.
This behavior is intentional, as it prevents conflicts when different schemas contain objects with the same name.
## How to fix this
-If you want to use the objects without specifying a schema, you'd need to put it first. Else, you should initialise the Supabase client with the schema([”With custom schemas”](https://supabase.com/docs/reference/javascript/initializing)) or specify the schema on each request using ".schema('your_schema')" (["Switching schemas per query"](https://supabase.com/docs/reference/javascript/select))
+If you want to use the objects without specifying a schema, you'd need to put it first. Else, you should initialise the Supabase client with the schema([”With custom schemas”](/docs/reference/javascript/initializing)) or specify the schema on each request using ".schema('your_schema')" (["Switching schemas per query"](/docs/reference/javascript/select))
diff --git a/apps/docs/content/troubleshooting/schema-pg_pgrst_no_exposed_schemas-does-not-exist b/apps/docs/content/troubleshooting/schema-pg_pgrst_no_exposed_schemas-does-not-exist.mdx
similarity index 70%
rename from apps/docs/content/troubleshooting/schema-pg_pgrst_no_exposed_schemas-does-not-exist
rename to apps/docs/content/troubleshooting/schema-pg_pgrst_no_exposed_schemas-does-not-exist.mdx
index 853f108969b..a4247cfaabc 100644
--- a/apps/docs/content/troubleshooting/schema-pg_pgrst_no_exposed_schemas-does-not-exist
+++ b/apps/docs/content/troubleshooting/schema-pg_pgrst_no_exposed_schemas-does-not-exist.mdx
@@ -1,9 +1,9 @@
---
title = "schema \"pg_pgrst_no_exposed_schemas\" does not exist"
topics = [
- "database",
- "rest-api",
- "platform"
+"database",
+"rest-api",
+"platform"
]
[[errors]]
message = "schema pg_pgrst_no_exposed_schemas does not exist"
@@ -16,6 +16,6 @@ PostgREST logs showing the error:
## Why this happens
- This error is seen when the Data API is disabled on the Supabase project.
-- Currently, we don’t really shutdown postgrest when data api is disabled. You will see a schema called `pg_pgrst_no_exposed_schemas` added in the exposed schemas.
+- Currently, we don't really shutdown PostgREST when the Data API is disabled. You will see a schema called `pg_pgrst_no_exposed_schemas` added in the exposed schemas.
- This should not adversely affect the project, although it may result in additional entries in your logs.
- We're aware of this issue and are working on it.