db4o Developer Community

February 2008 - Posts

• [Kudos] Developers can focus on the domain model and the value-add code, rather than data persistence

  If you are not familiar with db4objects ( DB4O ), it is an object oriented database. What does that mean? If I boil it down in laymen's terms : it is a database without tables or columns. [...] I did not have to do anything to setup how to save a User Read More... Posted Thursday, February 28, 2008 6:27 PM by German Viscuso | 0 Comments Filed under: Kudos

• [Kudos] LINQ for Java should look a lot more like db4o than Quaere

  LINQ for Java should look a lot more like db4o than Quaere. An independent project to do something like db4o's native queries would be nice. Maybe sit on top of JPA for ORM, or something like that. http://tomobag.blogspot.com/2008/02/linq-for-java.htm Read More... Posted Tuesday, February 26, 2008 5:26 AM by German Viscuso | 0 Comments

• [Kudos] Database access made stupidly simple

  Last time I had to develop a standalone application which would rely on a database, I had to design the whole data model, deploy it into a RDBMS, implement DAO s for CRUD operations and, only then, implement my business logic. Nowadays, things are so Read More... Posted Monday, February 18, 2008 4:09 PM by German Viscuso | 0 Comments

• [Kudos] db4o is as transparent as I imagined data storing should be

  “I like db4o because it has a very simple API, a small footprint but also allows dealing with complexity. It is as transparent as I imagined data storing should be. There is no need to modify your domain classes at all.” Gerd Klevesaat (Author of Eclipse Read More... Posted Friday, February 08, 2008 10:35 AM by German Viscuso | 0 Comments