对 Berkeley DB SQL API 数据库进行分区
使用 SQL API 时是否可以对 Berkeley DB 进行分区?我发现 Berkeley DB 支持使用 BTree 和哈希访问方法进行分区(http://download.oracle.com/docs/cd/E17076_02/html/programmer_reference/am_partition.html)。但没有说明是否可以使用 SQL API 来完成此操作。我的想法是创建原始 Berkeley DB 分区,然后使用 SQL API 打开它。有人尝试过对 SQL API Berkeley DB 进行分区吗?
Is it possible to have Berkeley DB partitioned when using SQL API? I found out that Berkeley DB supports partitioning (http://download.oracle.com/docs/cd/E17076_02/html/programmer_reference/am_partition.html) with BTree and Hash access methods. But there is no explanation weather it is possible to do it with SQL API. My idea is to create raw Berkeley DB partitioned and then open it using SQL API. Does anyone tried to partition SQL API Berkeley DB?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
David Segleau,Berkeley DB 产品管理总监。一般来说,我们建议人们在 Berkeley DB 论坛 上提问。您会在那里找到一个由活跃的 Berkeley DB 应用程序开发人员组成的大型社区。
你的问题的简短答案是“还没有”。 BDB 工程团队正忙于将 BDB 功能与 SQLite API 集成。对我们来说重要的是仔细考虑实现,使其非常易于使用,并且对于 SQLite 开发人员来说是一个“自然”的扩展。请继续关注您附近未来的 BDB 版本。
同时,BDB中的分区数据库大多是语法糖。它实际上是作为一种特殊情况实现的,下面有单独的表用于存储。您可以通过将数据拆分到单独的表中并修改应用程序以将数据获取/放入适当的表中来实现几乎相同的行为,就像现在一样。这有帮助吗?
当我们努力确定下一步要集成哪些 BDB 功能的优先级时,听取用户关于他们如何使用该产品的信息总是很有用的。您能否描述一下在您的应用程序中如何使用表分区以及它将解决哪些技术要求或问题?
谢谢,
戴夫
David Segleau, Director of Product Management for Berkeley DB here. Generally, we recommend that people ask questions on the Berkeley DB forums. You'll find a large community of active Berkeley DB application developers there.
The short answer to your question is "Not yet". The BDB engineering team is busy integrating BDB features with the SQLite API. The important thing for us is to think through the implementation so that it's very easy to use and is a "natural" extension for a SQLite developer. Stay tuned to a future BDB release near you.
In the meantime, in BDB partitioned databases are are mostly syntactic sugar. It's actually implemented as a special case, with separate tables used for storage underneath. You can accomplish close to the same behavior by splitting the data into separate tables and modifying your application to get/put data into the appropriate table as you would today. Does that help?
As we work on prioritizing which BDB features to integrate next, it's always useful to hear from our users about how they use the product. Can you describe how table partitioning would be used in your application and what technical requirements or problems it would solve?
Thanks,
Dave