4 ms·

The query is: select * from html where url="http://news.ycombinator.com/" and xpath='//tr/td/a[substring(@href,1,4)="http"][@href!="http://ycombinator.com"

The query is: select * from html where url="http://news.ycombinator.com/" and xpath='//tr/td/a[substring(@href,1,4)="http"][@href!="http://ycombinator.com"]' You can play with it yourself here (needs yahoo login): http://developer.yahoo.com/yql/console/ http://developer.yahoo.com/yql/console/

Sephr 18y ago
YQL isn't that great server-side until they add an `Access-Control-Allow-Origin: *` header. I'm pretty disappointed that they completely disallow Javascript access.
- spullara 18y ago
  It offers JSONP instead so you can access any YQL content via Javascript in a browser via script nodes.
  - Sephr 18y ago
    You still have to give Yahoo! complete control with that method. With XHR, Yahoo! has no control over your webpage.
    - spullara 18y ago
      It only it works in a few browsers but doesn't seem like it would hurt anything to add it. Thanks for the suggestion!
      - sachinag 18y ago
        I love how HN is the only site where "[x] would be cool" turns into a feature request implemented by the vendor.
        spullara 18y ago
        Nah, we do the same thing for things suggested on Twitter :)
thorax 18y ago
You know, honestly, I wasn't grokking much about how cool YQL could be until I saw this example. This helps a lot. Thanks.
henning 18y ago
I don't get it. Don't queries like that suffer from the same problems as normal screen scraping?
- jfarmer 18y ago
  Yeah, they're obviously brittle, but it's baby steps, y'know? I think it's pretty crazy that you can now scrape well-marked pages with a SQL-like syntax.