In Postgres, there is a limitation that prevents more than 100 arguments from being passed to a function. This limitation also applies to lists and maps constructed using the functions agtype_build_list and agtype_build_map. As a result, the size of lists and maps is restricted to a maximum of 100 elements.
SELECT * FROM cypher('test', $$
RETURN [1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1]
$$) AS (res agtype);
ERROR: cannot pass more than 100 arguments to a function
The same restriction applies to map properties.
SELECT agtype_build_list('[1, 1, 1]'::agtype);
agtype_build_list
-------------------
[[1, 1, 1]]
(1 row)
In Postgres, there is a limitation that prevents more than 100 arguments from being passed to a function. This limitation also applies to lists and maps constructed using the functions
agtype_build_listandagtype_build_map. As a result, the size of lists and maps is restricted to a maximum of 100 elements.The same restriction applies to map properties.
Why:
Implementation:
Change
agtype_build_listandagtype_build_mapto accept oneagtypeargument instead ofVARIADIC "any"Setup:
Apache AGE (master) - PostgreSQL 11.18