The Definitive Guide to db4o
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 convi- ingly 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.
What people are saying - Write a review
We haven't found any reviews in the usual places.
Other editions - View all
_name activation depth Address object application array ASP.NET C# and Java callback CasualEmployee Chapter client client/server mode commit configuration constraint constructor container create Customer object data model database file db.Close db.set(new db4o database db4objects default defined delete developers embedded Employee object encryption example Expert field foreign key Hibernate HSQLDB implement interface JAVA package JDBC look Manager mapping method MySQL Native Queries node null object data model object database object graph object model object-oriented object-relational mapping ObjectContainer ObjectContainer db ObjectManager ObjectServer ObjectSet result ODMG output password performance persistence Person class Person objects Project public boolean public class public String public void RDBMS relational database relational model relationships replication retrieve schema semaphore simple specified stored object String name tables transaction update UUIDs version numbers XTEA
Page 10 - Using tables to store objects is like drivingyour car horne and then disassembling it in the garage. It can be assembled again in the morning, but one eventually asks whether this is the most efficient way to park a car.
Page 10 - This is the ability to directly manipulate data stored in a database using an object programming language rather than using embedded SQL.
Page 1 - Acknowledgments I his book could not have been written without the support of professionals, friends, and the community.