From 1ca3c983e63bab470a1e5e57bddd8fa2bc72cac0 Mon Sep 17 00:00:00 2001 From: Taimoor Zaeem Date: Thu, 19 Feb 2026 13:07:57 +0500 Subject: [PATCH] docs: add NULL filtering section for domain representations Signed-off-by: Taimoor Zaeem --- docs/references/api/domain_representations.rst | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/docs/references/api/domain_representations.rst b/docs/references/api/domain_representations.rst index caa579e550..4822457b61 100644 --- a/docs/references/api/domain_representations.rst +++ b/docs/references/api/domain_representations.rst @@ -158,6 +158,13 @@ Note that on the database side we have our regular ``uuid`` format. If there's no CAST from ``json`` to ``app_uuid`` defined, the request body will still work with the native uuid format (``cc7ec76c-5254-4dfc-bf19-9a70ba2ae9b9``). +Domain NULL filtering +===================== + +Domains inherit the base type's NULL semantics. + +PostgREST does not support changing ``is.null`` operator semantics on domain types. It translates directly to SQL ``IS NULL`` at query level and so the meaning of NULL cannot be changed. For more details, see this `github issue `_. + Advantages over Views =====================