IMPORTANT

As you may notice, this page and pretty much the entire website were obviously created with the help of AI. I wonder how you could tell? Was it a big "Written With Claude" badge on every page? I moved it to the top now (with the help of AI of course) to make it even more obvious. There are a few blogposts that were written by me manually, the old-fashioned way, I hope there will be more in the future, and those have a similar "Human Written" badge. This project (not the website), on the other hand, is a very, very different story. It took me more than two years of painstaking and unpaid work in my own free time. A story that, hopefully, I will tell someday. But meanwhile, what would you like me to do? To create a complex documentation website with a bunch of highly technical articles with the help of AI and fake it, to give you an illusion that I also did that manually? Like the half of itnernet is doing at this point? How does that makes any sense? Is that even fair to you? Or maybe to create this website manually, the old-fashioned way, just for you? While working a paid job for a salary, most of you wouldn't even get up in the morning. Would you like me to sing you a song while we're at it? For your personal entertainment? Seriously, get a grip. Do you find this information less valuable because of the way this website was created? I give my best to fix it to keep the information as accurate as possible, and I think it is very accurate at this point. If you find some mistakes, inaccurancies or problems, there is a comment section at the bottom of every page, which I also made with the help of the AI. And I woould very much appreciate if you leave your feedback there. Look, I'm just a guy who likes SQL, that's all. If you don't approve of how this website was constructed and the use of AI tools, I suggest closing this page and never wever coming back. And good riddance. And I would ban your access if I could know how. Thank you for your attention to this matter.

RESPONSE_NULL_HANDLING

Also known as

response_null, text_response_null_handling (with or without @ prefix)

Control how NULL results are returned in plain text responses when the execution returns NULL from the database.

Syntax

@response_null <mode>
@response_null_handling <mode>
@text_response_null_handling <mode>

Values

Value	Description
`empty_string`	Returns an empty string response with status code 200 OK (default)
`null_literal`	Returns a string literal "NULL" with status code 200 OK
`no_content` or `204_no_content`	Returns status code 204 NO CONTENT

Examples

Return Empty String for NULL

sql

comment on function get_value(_id int) is
'HTTP GET
@response_null empty_string';

If result is NULL → Response body: ""

Return 204 for NULL

sql

comment on function find_record(_id int) is
'HTTP GET
@response_null 204_no_content';

If result is NULL → HTTP 204 with no body

Return JSON null

sql

comment on function get_optional(_key text) is
'HTTP GET
@response_null null_literal';

If result is NULL → Response body: null

Configuration Default

You can set the default behavior for all endpoints in appsettings.json:

json

{
  "NpgsqlRest": {
    "TextResponseNullHandling": "NoContent"
  }
}

Available values: EmptyString (default), NullLiteral, NoContent.

This sets the default for all endpoints, which can then be overridden per-endpoint using comment annotations.

NpgsqlRest Options configuration - Configure default null handling
Comment Annotations Guide - How annotations work
Configuration Guide - How configuration works

QUERY_STRING_NULL_HANDLING - NULL in query strings

Comments