根据我的经验，stream 表不完整。使用 FQL 查询全表会导致缺少条目。解决方法是查询条目的原始表，例如 status 表：
SELECT uid, status_id, time, source, message FROM status WHERE uid = me()
这更完整。显然，您必须并行查询 photo 表和其他表。为了不浪费太多时间，您可以批量查询。
然而，stream 表似乎适合来自朋友的帖子。
除了多个查询之外，一个缺点是其他表没有有关喜欢或评论的附加元信息，因此需要在第二步中检索这些信息。
From my experience, the stream table is incomplete. Using FQL to query the full table results in missing entries. A workaround is to query to original tables of the entries, e.g. the status table:
SELECT uid, status_id, time, source, message FROM status WHERE uid = me()
This is more complete. Obviously, you would have to query the photo table and others in parallel. In order to not loose too much time, you can batch the queries.
The stream table, however, seems to be fine for posts originating from friends.
A downside - apart from the multiple queries - is that the other tables don't have additional meta information about likes or comments, so these need to be retrieved in a second step then.
发布评论
评论（1）
根据我的经验，
stream表不完整。使用 FQL 查询全表会导致缺少条目。解决方法是查询条目的原始表，例如status表：这更完整。显然，您必须并行查询
photo表和其他表。为了不浪费太多时间，您可以批量查询。然而，
stream表似乎适合来自朋友的帖子。除了多个查询之外，一个缺点是其他表没有有关喜欢或评论的附加元信息，因此需要在第二步中检索这些信息。
From my experience, the
streamtable is incomplete. Using FQL to query the full table results in missing entries. A workaround is to query to original tables of the entries, e.g. thestatustable:This is more complete. Obviously, you would have to query the
phototable and others in parallel. In order to not loose too much time, you can batch the queries.The
streamtable, however, seems to be fine for posts originating from friends.A downside - apart from the multiple queries - is that the other tables don't have additional meta information about likes or comments, so these need to be retrieved in a second step then.