问题描述
其他人询问了使用 SQL 和 NoSQL一起，以及随后是否有一种干净的方式来定义访问对象以一种干净、通用的方式.
Other folks have asked about using SQL and NoSQL together, and subsequently whether there's a clean way of defining the access objects in a clean, generic way.
我的问题有点相关——java.sql 和 javax.sql 的哪些部分可以重用，Oracle* 是否有任何计划进入 NoSQL 空间并希望提供API?我知道 各种 NoSQL 选项差异很大，因此拥有JDBC"似乎没有意义.
My question is somewhat related -- which parts of java.sql and javax.sql can be re-used, and is there any plan for Oracle* to get into the NoSQL space and hopefully provide an API? I know that the various NoSQL options differ quite a lot, hence having a "JDBC" doesn't seem to make sense.
PS 我喜欢 David Pollack 为 Lift 所做的事情 Record 和 DBRecord.
PS I like what David Pollack is doing for Lift with Record and DBRecord.
***** 那是现在拥有 Java 的 Oracle，而不是 Oracle 数据库.
***** That's Oracle-who-now-owns-Java, not Oracle-the-database.
推荐答案
现在，每个 NoSQL 引擎(Cassandra、Neo4J、HBase 等)都提供了自己的访问 API.这些API并不统一，绝对不是基于java.sql"和javax.sql".
Now, each NoSQL engine (Cassandra, Neo4J, HBase, etc.) provides its own access API. Theses APIs are not unified, and are absolutely not based on "java.sql" nor "javax.sql".
所以，现在，我认为尝试将这些包与 NoSQL 数据库一起使用是没有意义的.但我希望通过类别(例如面向列、图形、文档数据库)将这些产品与通用 API(和/或查询语言)统一起来.
So, now, I think it makes no sense to try using theses packages with NoSQL databases. But I'm hoping for a unification of theses products with a common API (and/or query language) by category (column-oriented, graph, document databases for example).
这篇关于java.sql 和 javax.sql 中的某些接口可以重用于 NoSQL 吗?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！