Dynamic SQL
Is there anything wrong using something like this: https://www.postgresql.org/docs/current/ecpg-dynamic.html in a RPC function?
I would like to use it to build dynamic queries depending on the filters the user wants to apply to the query.
With PostgREST, it seems that it's not possible to filter selected data on properties that you don't have selected in the query. Which annoys me a bit, since I don't need these properties, and this consumes unnecessary bandwidth etc.
Also there are currently some limitations with PostgREST and the Supabase API integration which makes it harder to use the two together for my use case.
Using this, I could build queries with table unions, filtering selected data without having to add extra properties, and do other things more easily.
I would like to use it to build dynamic queries depending on the filters the user wants to apply to the query.
With PostgREST, it seems that it's not possible to filter selected data on properties that you don't have selected in the query. Which annoys me a bit, since I don't need these properties, and this consumes unnecessary bandwidth etc.
Also there are currently some limitations with PostgREST and the Supabase API integration which makes it harder to use the two together for my use case.
Using this, I could build queries with table unions, filtering selected data without having to add extra properties, and do other things more easily.
PostgreSQL Documentation
36.5. Dynamic SQL 36.5.1. Executing Statements without a Result Set 36.5.2. Executing a Statement with Input Parameters 36.5.3. Executing a Statement …
