Skip to content

docs: add NULL filtering section for domain representations #4662

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
taimoorzaeem wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

docs: add NULL filtering section for domain representations #4662

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions docs/references/api/domain_representations.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 <https://github.com/PostgREST/postgrest/issues/4612>`_.

Comment on lines +161 to +167
Copy link
Member

@steve-chavez steve-chavez Feb 24, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not agreeing for now, the limitation looks bad. Perhaps there's a solution, see #4612 (comment).

Advantages over Views
=====================

Expand Down