Skip to content
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.

REQUEST_PARAM_TYPE

Also known as

param_type (with or without @ prefix)

Control how parameters are transmitted to the endpoint - via query string or request body.

Syntax

@request_param_type <type>
@param_type <type>

type: query_string, query, body, body_json

Values

ValueDescription
query_stringParameters from URL query string
querySame as query_string
body_jsonParameters from JSON request body
bodySame as body_json

Default Behavior

When not specified:

  • GET and DELETE methods use query string
  • All other methods use JSON body

Examples

Force Query String Parameters

sql
create function search_users(_name text, _active bool)
returns setof users
language sql
as $$select * from users where name ilike '%' || _name || '%' and active = _active$$;

comment on function search_users(text, bool) is
'HTTP GET
@request_param_type query_string';

Request: GET /api/search-users?_name=john&_active=true

Force JSON Body Parameters

sql
create function get_filtered_data(_filters text)
returns json
language sql
as $$...$$;

comment on function get_filtered_data(text) is
'HTTP GET
@request_param_type body_json';

Request:

http
GET /api/get-filtered-data
Content-Type: application/json

{"_filters": "status=active"}

Short Form Keywords

sql
-- Using '@param_type' instead of '@request_param_type'
comment on function func1(text) is
'HTTP
@param_type query';

-- Using 'BODY' (case-insensitive)
comment on function func2(text) is
'HTTP
@param_type BODY';

POST with Query String

Override the default body behavior for POST:

sql
create function quick_action(_id int)
returns text
language sql
as $$...$$;

comment on function quick_action(int) is
'HTTP POST
@param_type query_string';

Request: POST /api/quick-action?_id=123

Behavior

When parameter type doesn't match the request format, the endpoint returns 404 Not Found:

  • Endpoint configured for query_string but receives JSON body → 404
  • Endpoint configured for body_json but receives query parameters → 404

Comments

Released under the MIT License.