db4o造句怎么写

8、Fortunately, there are a couple of ways to teach db4o how to manage the transition.

10、In particular, I'll introduce the various mechanisms available for retrieving, modifying, and restoring objects back into db4o.

12、For my exploration testing of db4o, I'm going to use the JUnit 4 test library in console mode.

14、上一次我使用了db4o的QBE引擎演示了数据检索，这里将快速回顾一下。

16、If db4o supports extends, then it also must support implements, which makes for a pretty powerful query capability, as you'll see.

18、So far in this series, I've used the Person type to reveal almost all of the fundamentals of working with db4o.

20、考察db4o的这个领域是一项棘手的任务，也给了我一个机会展示一位好友教给我的策略：探察测试。

22、在db4o系统中，打开第二个数据库逻辑连接非常简单，即使当数据库驻留在本地磁盘上时也是如此。

24、正如我所说的，在当今的面向对象世界里，与关系数据库相比，db4o这样的对象数据库可以为面向对象开发人员提供更多的功能。

1、The db4o home page: Learn more about db4o.

3、Querying db4o using SQL via JDO or JPA, using sql4o.

5、This turns out to be a pretty consistent theme throughout the db4o refactoring story: Wherever possible, db4o silently deals with version mismatches.

7、If you haven't already done so, you may want to download db4o now.

11、实际上，db4o向后兼容的妙法值得解释一下。

15、Something like this is a drastic change to db4o because it stores objects in a manner that keys off of classname.

19、换句话说，激活深度表示从根对象中标识的引用总数，db4o将在查询中遍历根对象并返回结果。

23、这里最重要的一点是，db4o 静默地处理它看到的磁盘上的数据与类型定义之间的不匹配。

2、Listing 11. A db4o native query.

6、Understanding how an OODBMS like db4o stores associated objects held through references is a tricky business.

13、后来话题转移到7.0版的db4o中的新特*上

21、理解像db4o这样的OODBMS是如何通过引用存储相关对象，是比较复杂的事情。

4、这成为贯穿db4o重构行为的永恒主题：db4o尽可能静默地处理版本失配。

17、db4o近来获得了快速的发展，Db4Object最近发布了他们的旗舰产品db4o——嵌入式odbms的7.0版本，并宣布他们的开源odbms已有超过30000个布署。

9、Fortunately, the db4o system, like most OODBMS systems, has an integral understanding of inheritance.

25、db4o对此采用了折衷的办法，限制所检索的对象数量，使用称为激活深度(activation depth)的方法，它指明在对象图中进行检索的最低层。