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
Like we have with deno module definition. It will be nice and powerful if we have a way to define Postgres functions and Views as part of the schema type definition.
if we have a function type (to represent functions and views ) and we define properties like 1. function-type (query or mutation or view) via attribute 2. input parameter (scalar or custom types) 3. return values (scalar or other type) and a function body as string . for e,g
The function definition can be pulled from functions.sql matching name, input and output as a way of validating before applying . The query functions can be part of the query. Note that this can also apply to existing postgres db functions (in that case, no sql file name is passed as parameter to the postgres directive )
The text was updated successfully, but these errors were encountered:
Like we have with deno module definition. It will be nice and powerful if we have a way to define Postgres functions and Views as part of the schema type definition.
if we have a function type (to represent functions and views ) and we define properties like 1. function-type (query or mutation or view) via attribute 2. input parameter (scalar or custom types) 3. return values (scalar or other type) and a function body as string . for e,g
The function definition can be pulled from functions.sql matching name, input and output as a way of validating before applying . The query functions can be part of the query. Note that this can also apply to existing postgres db functions (in that case, no sql file name is passed as parameter to the postgres directive )
The text was updated successfully, but these errors were encountered: