From 85a4e35a2de869ddf9b6c5f6893a3154767cbc76 Mon Sep 17 00:00:00 2001 From: Laurence Isla Date: Wed, 24 Apr 2024 15:04:35 -0500 Subject: [PATCH] docs: fix http status for PGRST121 error --- docs/references/errors.rst | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/docs/references/errors.rst b/docs/references/errors.rst index 40a5ba79f..a4ff1a987 100644 --- a/docs/references/errors.rst +++ b/docs/references/errors.rst @@ -247,7 +247,7 @@ Related to the HTTP request elements. | | | ``is.null`` or ``not.is.null`` :ref:`operators `.| | PGRST120 | | | +---------------+-------------+-------------------------------------------------------------+ -| .. _pgrst121: | 400 | PostgREST can't parse the JSON objects in RAISE | +| .. _pgrst121: | 500 | PostgREST can't parse the JSON objects in RAISE | | | | ``PGRST`` error. See :ref:`raise headers `. | | PGRST121 | | | +---------------+-------------+-------------------------------------------------------------+ @@ -425,5 +425,3 @@ For non standard HTTP status, you can optionally add ``status_text`` to describe detail = '{"status":419,"status_text":"Page Expired","headers":{"X-Powered-By":"Nerd Rage"}}'; If PostgREST can't parse the JSON objects ``message`` and ``detail``, it will throw a ``PGRST121`` error. See :ref:`Errors from PostgREST`. - -