Sometimes we make things more difficult for ourselves than they really need to be. Programmers
are no exception to this. For example, those of us of an object-oriented persuasion devote time
and expertise to creating a model of a problem domain in terms of objects. We produce solutions
that model real-world objects and that are highly extensible and reusable. And then we decide
that we need those objects to stick around after the program stops, so we go ahead and create
another, totally different model, just so that we can use a database. Our carefully designed
objects are then chopped and squeezed to fit this new data model.
In fact, most developers would argue that object persistence is a fundamental problem
that has yet to be adequately solved. While there are frameworks that hide some of the details
of the mismatch between object and data models from the programmer, none of them convincingly
make what should be a simple job really simple. We held the same opinion, until we found
out about db4o. db4o—the database for objects—simply stores native objects. “Native” means
that these are the objects that your C# or Java program creates, stored exactly as they are. There’s
no need to create a database schema, no need to map objects to tables, no need to do anything
really, except store objects. Problem solved!
具體描述
讀後感
評分
評分
評分
評分
用戶評價
相關圖書
本站所有內容均為互聯網搜索引擎提供的公開搜索信息，本站不存儲任何數據與內容，任何內容與數據均與本站無關，如有需要請聯繫相關搜索引擎包括但不限於百度，google,bing,sogou 等
© 2025 qciss.net All Rights Reserved. 小哈圖書下載中心 版权所有