FQL 子查询破坏顶级查询并且永不返回
我们有一个 FQL 查询,以前可以正常工作,但在 10 月 16 日左右停止了。Facebook 对此没有提供任何帮助。
这段代码曾经有效:
SELECT object_id, metric, end_time, period, value
FROM insights
WHERE object_id IN
(
SELECT page_id
FROM page_admin
WHERE uid=123
AND page_id<>456
AND page_id<>789
)
AND metric="page_audio_plays"
AND end_time=end_time_date("2011-11-11" )
AND period=86400
如果我运行内部 Select,它会返回一个很大的 page_id 列表。如果我删除内部选择并替换为逗号分隔的 id 列表,如下所示:
...where object_id in ( 123, 456, 8778, 999)
整个查询运行。
使用上面的原始代码,查询永远不会返回并超时。
问:有人知道 FB 方面在 10 月中旬左右发生了这方面的问题吗?或者像这样的子查询有本质上的错误吗?
关于如何解决的任何建议?
We have a FQL query that used to work and stopped somewhere around Oct 16. No help from Facebook on this.
This code used to work:
SELECT object_id, metric, end_time, period, value
FROM insights
WHERE object_id IN
(
SELECT page_id
FROM page_admin
WHERE uid=123
AND page_id<>456
AND page_id<>789
)
AND metric="page_audio_plays"
AND end_time=end_time_date("2011-11-11" )
AND period=86400
If I run the inner Select, it returns a large list of page_id's. IF I remove the inner select and replace with a list of comma seperated id's like this:
...where object_id in ( 123, 456, 8778, 999)
The overall query runs.
With the original code above, the query never returns and times out.
Question: Is anyone aware of something on FB side that broke around the middle of October in this regards? Or is there something inherently wrong with doing a subquery like this?
Any suggestions on how to work around?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
Net:查询返回了太多数据。如果遇到此问题,请以某种方式分解结果集,以便它返回较小的数据集。如果 API 返回一些可辨别的状态告诉你,那就太好了,但是......
Net: query returned TOO much data. If you have this problem, break up the result set somehow so it returns a smaller set of data. Would be nice if API returned some discernable status telling you so but....