Re: Clean Object Class Design -- What is it?

Bob Badour wrote:
> I started this thread because the representative of an OODB vendor
> made the claim that a clean object class design will obviate normalization
> and that his company's OODB obviates database design. The same vendor
> representative also made the extraordinary claim that the OODB does not
> require any administration. You just create your Java classes and wham!
> you have a database.

Right!
Thanks for quoting me over and over.

No matter how often you deny it:
This works perfectly for embedding our database into applications or Tomcat webapps.

...with zero administration work for creating tables, triggers, stored procedures, joins, fetching pkeys and all the other unnecessary relational troubles.

...and better performance since all SQL, JDBC, ODBC driver overhead is unnecessary.

...and factor 10 advantages during refactoring since the system is typesafe and there is only one single place, where changes need to be applied: the Java class.

> Can I assume you expect a database design independent
> of application design?

We are working on a concept that we will call "namespace friends". It will allow to use the same stored object with different classes for different applications.

Kind regards,
Carl

---
Carl Rosenberger
db4o - database for objects - http://www.db4o.com