Sandro Santilli
Sandro Santilli
Uhm, this ticket is getting confusing. When I filed it I was thinking about named queries, not functions. I don't really see the value added in calling functions with /my_function/param1_value/param2_value...
Users should use cartodb.js, right ? That gives them clean API. Mine is purely to enhance cacheability, correct.
I like the idea of allowing developers to define their own API inside the database. This means preparing the database somehow (creating functions/views/triggers in it). Using "named queries" would be...
a named query could call any function (ie: `select * from my_custom_function({0}, {1}, {3})`)
https://github.com/Vizzuality/CartoDB-SQL-API/wiki/Named-Queries-API
Yes, I think we should define a function to populate the store containing named queries. This store is not the "cdb_functionmetadata" though, that one is for something else. The wiki...
As "named maps" has been implemented in the cartodb tiler (https://github.com/CartoDB/Windshaft-cartodb/issues/98) we could aim at using a similar/compatible interface for "named queries". The difference between current proposal (Named-Queries-API wiki page)...
Wiki page stubbed and renamed to https://github.com/CartoDB/CartoDB-SQL-API/wiki/Named-Queries. Question: do we need "authentication tokens" ?
Do we also allow different database users to create their named functions ? Same thing than with the tiler. By keeping different users separated we don't have to deal with...
NOTE: we're pending that brainstorming session :)