db-ojb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Guillaume Nodet" <guillaume.no...@deliasystems.com>
Subject Optimization when storing new objects
Date Thu, 05 Feb 2004 09:13:11 GMT
When inserting new objects in the database, would it be possible to avoid
trying to materialize them ?
For example when storing an object in ojb, ojb first tries to materialize
it.
If this fails, ojb passes true in the 'insert' parameter to the storeToDb
method.
This parameter is given to the storeCollections method, but when collections
are 1-n
with cascade store on, the parameter is not given to the store method.
Would it be possible to call the store(Object obj, Identity oid,
ClassDescriptor cld, boolean insert)
instead to avoid trying to materialize the object when we know that is does
not exists ?

Regards,

Guillaume



---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org


Mime
View raw message