doujinyi1267 2016-09-24 01:58
浏览 28
已采纳

AppEngine / Datastore:检索最佳方法,因为祖先查询以递归方式返回所有内容

When I do a get() with an ancestor constraint, it seems like I get all entities for that ancestor key and all ancestors that it is parent to.

In this case, I am using ancestral relationships to represent a homogenous tree (all nodes represented by the same kind; every level is immediately consistent). All of the IDs I am using are globally unique and I have the parent-ID written on each entity (in addition to it being in the ancestor path).

Since the by-ancestor retrieval returns too much data (all levels at and below rather than just the immediate level; The documentation doesn't mention this and a couple of others eccentricities), I'll need to add a filter to make sure I just get back the current level.

So, the question is whether there's a difference in efficiency to do a ancestor().filter() versus just filter() since these both produce the same results for me.

Thanks.

  • 写回答

1条回答 默认 最新

  • douzhongjian0752 2016-09-24 03:41
    关注

    Just filter() is eventually consistent, whereas ancestor().filter() is strongly consistent.

    As you mentioned, you'll need to filter by an indexed a property to just get a particular level of the tree back.

    本回答被题主选为最佳回答 , 对您是否有帮助呢?
    评论

报告相同问题?

悬赏问题

  • ¥15 远程桌面文档内容复制粘贴,格式会变化
  • ¥15 关于#java#的问题:找一份能快速看完mooc视频的代码
  • ¥15 这种微信登录授权 谁可以做啊
  • ¥15 请问我该如何添加自己的数据去运行蚁群算法代码
  • ¥20 用HslCommunication 连接欧姆龙 plc有时会连接失败。报异常为“未知错误”
  • ¥15 网络设备配置与管理这个该怎么弄
  • ¥20 机器学习能否像多层线性模型一样处理嵌套数据
  • ¥20 西门子S7-Graph,S7-300,梯形图
  • ¥50 用易语言http 访问不了网页
  • ¥50 safari浏览器fetch提交数据后数据丢失问题