Changelog for build 911

Posted by yqlteam on February 20, 2009 – 11:31 am
Filed under changelog
  • Console and web service now support an “env” query parameter. This is a url that points to an environment/shell file that YQL will load. Currently this enables multiple tables to be used at once.
  • “Use” table no longer requires the “as” clause. When “as” is absent it will default to the final path segment filename minus the extension. e.g. use 'http://somewhere/service.api.xml; select * from service.api;
  • Show tables now shows where the open data definition was defined
  • Desc table format tweaked
  • Open data table paging fixes, including better support for none paging but flexible result sized services and fixed page models. Moved “matrix” to the paging parent element.
  • Offset bug fixed in table(offset,number) processing

Changelog for build 822

Posted by yqlteam on February 5, 2009 – 8:31 pm
Filed under changelog
  • NOT LIKE added
  • MATCHES regex matching added
  • New USE verb for open data table importing
  • Support for open data table definitions

Open data tables added to YQL

Posted by yqlteam on February 5, 2009 – 12:53 pm
Filed under news

We’re pleased to announce that our last update now enables developers can create, use, and share table definitions over for any public API on the web, in addition to the Yahoo! APIs we support today.

For example, one of the requests we had when using our weather table was how to get an ID that would work for an international location. We pointed people to the weather.com API, but that needed a URL to be formatted up in a specific way. Now you can make that a table and use it:

use 'http://www.javarants.com/weather/weather.search.xml' as ws;
select * from weather.forecast where location in (select id from ws(1) where query='bonn, germany')

Try it.

While we believe this is a great start, it’s work in progress. We’re already adding more capabilities and adjusting the open data table XML syntax as we get feedback and go forward. You can read more about how to go about creating open data tables in our documentation.

Changelog for 2009.01.12.16:11

Posted by yqlteam on January 21, 2009 – 10:25 pm
Filed under changelog

New tables

  • upcoming.user
  • microformats
  • flickr.photos.sizes

Table updates

  • local.search “location” key is now optional
  • mybloglog user by service
  • fixed typo in mybloglog.members.find
  • “charset” is now an optional key in html table, to enable developers to force a particular charset to be used when parsing the web page

Bug fixes, including:

  • more html and xhtml and i18n issues fixed for html table
  • subselect fix for optional keys

Other:

  • publiclyCallable element in diagnostics is set to true if the query can work across the public entrypoint
  • show tables response format changed

Note: future releases will more strictly apply robots.txt to html table fetches