NpgsqlRest

Appearance

Comments
Written with Claude
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.

VOID ​

Also known as

void_result (with or without @ prefix)

Force an endpoint to return 204 No Content instead of a JSON response. All statements are executed for side effects only.

Available since version 3.12.0.

Syntax ​

code
@void
@void_result

Examples ​

Multi-Command Side Effects ​

Useful when all statements are side-effect-only (e.g., set_config calls followed by a DO block):

sql
sql
/* HTTP POST
@void
@param $1 message_text text
@param $2 _user_id text = null
*/
select set_config('app.message', $1, true);
select set_config('app.user_id', $2, true);
do $$ begin
    insert into messages (user_id, text)
    values (current_setting('app.user_id')::int, current_setting('app.message'));
end; $$;

Without @void, this returns {"result1":"...","result2":"...","result3":-1}. With @void, it returns 204 No Content.

This eliminates the need to add @skip to every individual statement.

Single-Command Void ​

Also works on single-command endpoints:

sql
sql
-- HTTP POST
-- @void
-- @param $1 key text
-- @param $2 value text
select set_config($1, $2, true);

Function Endpoints ​

Works on function and procedure endpoints too:

sql
sql
comment on function process_data(int) is '
HTTP POST
void
';

Behavior ​

  • All statements are executed normally via ExecuteNonQuery
  • The response status is 204 No Content with an empty body
  • No JSON wrapping, no result keys, no rows-affected counts
  • Works on all endpoint types: functions, procedures, CRUD, and SQL file endpoints
  • For multi-command SQL files, all statements execute sequentially — if any fails, the request fails
  • The Describe step still runs at startup — use @returns void instead if the statement would fail Describe

Comments