You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The default column name for a builtin function that is used in a cached query does not match the upstream (at least for PG). Upstream PG defaults the column name to the simple name of the function, whereas readyset will append the parameter types to the function name (see below).
Expected behavior
Match the upstream naming: only function name is used (PG)
Actual behavior
function name and parameter types
Steps to reproduce
$ create table dogs (id int, name varchar(64), birth_date timestamptz default CURRENT_TIMESTAMP);
$ select date_trunc('minute', birth_date::timestamp) from dogs where id = 2;
date_trunc
---------------------
2024-03-25 18:45:00
(1 row)
$ create cache from select date_trunc('minute', birth_date::timestamp) from dogs where id = 2;
$ select date_trunc('minute', birth_date::timestamp) from dogs where id = 2;
date_trunc('minute', (`public`.`dogs`.`birth_date`::TIMESTAMP))
-----------------------------------------------------------------
2024-03-25 18:45:00
(1 row)
Upstream DB type and version
PG, any version
The text was updated successfully, but these errors were encountered:
Summary
The default column name for a builtin function that is used in a cached query does not match the upstream (at least for PG). Upstream PG defaults the column name to the simple name of the function, whereas readyset will append the parameter types to the function name (see below).
Expected behavior
Match the upstream naming: only function name is used (PG)
Actual behavior
function name and parameter types
Steps to reproduce
Upstream DB type and version
PG, any version
The text was updated successfully, but these errors were encountered: