5 ms·
Fantastic news, nested batched queries on the graph API were a total crapshoot in some circumstances last time I tried (FQL works much better). I may have to u
by Groxx 14y ago
Fantastic news, nested batched queries on the graph API were a total crapshoot in some circumstances last time I tried (FQL works much better). I may have to update some code now...
- saurik 14y agoIs there an advantage to using the graph API over using FQL? It seemed to me like FQL was more flexible in that you could specify more complex and general queries using a unified interface; am I missing something? (I easily could be missing something: I find that the API changes so often it is difficult to keep up with.)
- Groxx 14y agoMostly simplicity. "graph.facebook.com/id/photos" is easier than multiple round trips or nested queries, and in general it's easier to grasp for people who aren't familiar with SQL (not me, but lots and lots of people never have to touch the stuff). Personally though, I find myself waffling between the two depending on which gives me the information I want, the most easily. Often that's the graph API, though speed can suffer immensely unless you only request the fields you need (e.g. counts add a lot of time to a request).