您可以在 FQL 中执行哪些使用 Graph API 无法执行的操作
我试图弄清楚在哪些情况下 FQL 具有 Graph API 所没有的功能。
我试图在文档中找到答案，但正如许多其他人指出的那样，它们并不是最清晰或最完整的。更困难的是，许多在开发者平台上发表评论的博客现在也已经过时了。
那么，FQL 能做什么 Graph API 不能做的事情呢？
I'm trying to figure out what are the cases where FQL has features which the Graph API doesn't.
I tried to find the answer in the docs, but as many others have pointed out, they aren't the clearest or the most complete. To make things more difficult, a lot of the blogs commenting on the Developer platform are now dated too.
So, what can FQL do that the Graph API can't?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
FQL 有一个 WHERE 子句，图形 API 没有任何等效项。我说的是比仅仅获取对象连接（例如用户的朋友）更复杂的事情。示例：获取用户的朋友，他们也是应用程序用户并且在线聊天，获取明天开始且不是由我自己创建的所有事件，等等。
除此之外，FQL 更像是图形 API 的扩展，而不是独立的东西，并且被使用对图形对象进行查询。
FQL has a WHERE clause, which graph API doesn't have any equivalent of. I'm talking of something more sophisticated than just getting object connections (like user's friends). Examples: get user's friends who are also app users and online in chat, get all events which start tomorrow and not created by myself, etc, etc.
Besides that FQL is more like an extension to the graph API rather than something independent and is used to make queries on graph objects.