Re: S.O.D.A. database Query API - call for comments

From: Carl Rosenberger <carl_at_db4o.com>
Date: Sat, 21 Jul 2001 18:01:59 GMT
Message-ID: <9cvdk2$eju$02$1@news.t-online.com>

Lee Fesperman wrote:
> FirstSQL/J uses SQL. A class is just another database type for a column.
 The only change
> to SQL is to allow you call the methods of a column object and a 'new'
 operator for
> creating objects.

With your approach there is no possibility for server-side query optimization. Every single object needs to be instantiated completely, just to evaluate a simple member. This will perform very badly.

> > Do you use Java serialization to store objects?
>
> Yes, in columns.

What do you do, if user classes are modified?

Serialization and deserialization is very slow and produces lots of storage overhead by the way.

What happens if:

- object A has a member B
- object A is stored to one column in one table
- object B is stored to another column in another table
- one query delivers object A
- another query delivers object B

How many instances of object B will be produced?

Kind regards,
Carl

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

Received on Sat Jul 21 2001 - 13:01:59 CDT