We've launched some pretty big updates during the last few months,
for running server side JS code in your Open Data Tables, and new verbs for modifying and updating data on the web. Our release today consists of a lot of features (and bug fixes) that have been identified by developers on twitter, on our forums, or by our colleagues and ourselves - we use YQL all the time and certain things annoy us too!
The two major new feature additions are: the
SET verb and the
SET enables you to configure static variables, such as API keys, secrets, and other required values, independently of YQL statements and web service calls. Why is this so useful? Consider the following example which uses the Guardian content search Open Data Table:
select * from guardian.content.search where api_key="1234567890" and q='environment'
Currently, every time I use the Guardian tables I need to send my API key - which really doesn't change very much. With
set, I can just define it