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.

CACHED

Enable server-side response caching for routine results.

Syntax

@cached
@cached <param1>, <param2>, <param3>, ...

Space-separated lists are also valid: @cached _year _department

Parameters specified become part of the cache key.

Examples

Simple Caching

sql
create function get_app_settings()
returns json
language sql
as $$select settings from app_config where id = 1$$;

comment on function get_app_settings() is
'HTTP GET
@cached';

Cache Key by Parameter

sql
create function get_user_profile(_user_id int)
returns json
language sql
as $$select row_to_json(u) from users u where id = _user_id$$;

comment on function get_user_profile(int) is
'HTTP GET
@cached _user_id';

Different _user_id values create separate cache entries.

Multiple Cache Key Parameters

sql
create function get_report(_year int, _department text)
returns json
language sql
as $$...$$;

comment on function get_report(int, text) is
'HTTP GET
@cached _year, _department';

With Cache Expiration

Cache expiration uses interval format:

sql
comment on function get_config() is
'HTTP GET
@cached
@cache_expires_in 1h';

Caching Set-Returning Functions

Caching works for set-returning functions and record types. When a cached function returns multiple rows, the entire result set is cached:

sql
create function get_all_users()
returns table(id int, name text)
language sql
as $$select id, name from users$$;

comment on function get_all_users() is
'HTTP GET
@cached
@cache_expires_in 5m';

Use MaxCacheableRows in Cache Options to limit the maximum number of rows that can be cached. Result sets exceeding this limit are returned but not cached.

Behavior

  • Caches the response for subsequent identical requests
  • Works with scalar results, set-returning functions, and record types
  • Cache key is based on specified parameters
  • Use with cache_expires_in to set expiration time

Cache Configuration

The cached annotation requires cache to be enabled in Cache Options configuration.

Two cache types are available:

TypeDescriptionUse Case
MemoryIn-memory cache on the application serverSingle instance deployments, development
RedisDistributed cache using RedisMulti-instance deployments, production

Example configuration:

json
{
  "CacheOptions": {
    "Enabled": true,
    "Type": "Memory"
  }
}

For Redis:

json
{
  "CacheOptions": {
    "Enabled": true,
    "Type": "Redis",
    "RedisConfiguration": "localhost:6379"
  }
}

See Cache Options for complete configuration reference.

Comments

Released under the MIT License.