Graph“类型”的 FQL 等效项是什么? /feed 调用中的字段?
我一直在使用图表来获取页面的提要/发布信息,但已开始使用 FQL,因为我需要按 Updated_time 排序,而不是按图表返回的标准created_time 排序。
我正在 FQL 中使用流表,我可以从中获取我需要的所有信息,除了“类型”字段的等效信息(即状态、链接、照片、视频等)。
当我将类型添加到 FQL 的字段列表中时,我得到一个 int 值(或 null),这似乎大致翻译为 46 =>页面状态,56 =>用户状态,80 =>链接...等,但该字段没有记录,并且该值似乎并不完全一致。我见过用户状态等于 56 或 237,但不确定上下文差异是什么使它们发生变化。
我使用的 FQL 是:
"SELECT post_id, type, message, description, comments, likes, created_time, updated_time FROM stream WHERE source_id = 40796308305 ORDER BY updated_time DESC" which I'm viewing through the Graph API Explorer /fql?q=
我可以通过存储 ids 并进行额外的图形调用(例如“?ids=12345,23456,34567&fields=type
”)来获取类型信息,但是目标是在同一次通话中实现这一点。 有谁知道如何/是否可以实现这一点?
非常感谢
I have been using the graph to obtain feed / post information for pages, but have started to use FQL instead as I needed to sort by updated_time rather than the standard created_time sort returned by the graph.
I am using the stream table in FQL and I can get all the information from this I require except the equivalent of the 'type' field (i.e. Status, Link, Photo, Video etc).
When I add type into the fields list for the FQL, I get a int value back (or null) which seems to roughly translate to 46 => page status, 56 => user status, 80 => link ... etc but this field is not documented and this value does not seem to be fully consistent. I've seen a user status be equal to 56 or 237, but not sure what the context difference is to make them change.
The FQL I'm using is:
"SELECT post_id, type, message, description, comments, likes, created_time, updated_time FROM stream WHERE source_id = 40796308305 ORDER BY updated_time DESC" which I'm viewing through the Graph API Explorer /fql?q=
I can get the type information by storing up the ids and making an additional graph call such as "?ids=12345,23456,34567&fields=type
" but the goal is to get this in the same call.
Does anybody know how / if this can be achieved?
Many Thanks
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
这被认为是一个错误。请参阅https://developers.facebook.com/bugs/223855374358566
This was acknowledged as a bug. See https://developers.facebook.com/bugs/223855374358566