Open nicolateral opened 4 years ago
Hi @nicodinh ,
I'm unable to reproduce the issue by creating a custom SQL function in non-public schema.
Please execute the following SQL query and comment down the results;
select * from hdb_catalog.hdb_function_info_agg where function_name = 'item_search';
Hi @rakeshkky ,
Please execute the following SQL query and comment down the results;
select * from hdb_catalog.hdb_function_info_agg where function_name = 'item_search';
This query returns an empty resultset.
The function does not appears in hdb_catalog.hdb_function_info_agg
. Can you paste in reply a function definition that is supposed to works ? I will tell you if it works in my pgw
schema.
@rakeshkky , I just tried to create a fake schema my_schema
in the console and then create my function in my_schema
. This works ... still investigate why this does not works under pgw
.
@nicolateral Is this still a problem?
@tirumaraiselvan hi, yes. I'm currently using
hasura/graphql-engine:v1.1.0 postgres:11.3
It seems that I cannot track functions on schema that begin with "pg". I tried some schema names ("pgw", "pgx" ...) and it does not works. But it works with ("prg", "my_schema").
@nicolateral Thanks for the report. I could reproduce this at my end as well. Changing the title to reflect the bug.
The issue has both server and console components:
Server: track_function
throws an error on schemas starting with "pg".
Console: Does not list track-able functions on schemas starting with "pg".
@tirumaraiselvan I think the console issue would be solved with the server fix as well. the console uses data in the hdb_catalog.hdb_function_agg
view to list the functions
Docker images hasura/graphql-engine:v1.1.0-beta.2 postgres:11.3
Issue It is the first time I try to track a function on non-public schema. I have this function "item_search" on schema "pgw" :
This function does not appears in the console.
I tried to track this function using the API :
Request (track_function:v1)
Request (track_function:v2)
Response
When I create this function on public schema (changing its name
pgp.item_search
topgp_item_search
), this works fine, as usual (the function appears in console and can be tracked using the API).