“db4o”簡單造句，db4o造句子

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.

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

17、db4o近來獲得了快速的發展，Db4Object最近發佈了他們的旗艦產品db4o——嵌入式odbms的7.0版本，並宣佈他們的開源odbms已有超過30000個佈署。

22、在db4o系統中，打開第二個數據庫邏輯連接非常簡單，即使當數據庫駐留在本地磁盤上時也是如此。

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

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

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

24、正如我所説的，在當今的面向對象世界裏，與關係數據庫相比，db4o這樣的對象數據庫可以為面向對象開發人員提供更多的功能。

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

14、上一次我使用了db4o的QBE引擎演示了數據檢索，這裏將快速回顧一下。

25、db4o對此採用了折衷的辦法，限制所檢索的對象數量，使用稱為激活深度(activation depth)的方法，它指明在對象圖中進行檢索的最低層。

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

21、理解像db4o這樣的OODBMS是如何通過引用存儲相關對象，是比較複雜的事情。

13、後來話題轉移到7.0版的db4o中的新特*上

4、這成為貫穿db4o重構行為的永恆主題：db4o儘可能靜默地處理版本失配。

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

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

20、考察db4o的這個領域是一項棘手的任務，也給了我一個機會展示一位好友教給我的策略：探察測試。

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