Return-Path: Delivered-To: apmail-db-ojb-dev-archive@www.apache.org Received: (qmail 4137 invoked from network); 5 Feb 2004 09:13:30 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 5 Feb 2004 09:13:30 -0000 Received: (qmail 77030 invoked by uid 500); 5 Feb 2004 09:13:02 -0000 Delivered-To: apmail-db-ojb-dev-archive@db.apache.org Received: (qmail 76977 invoked by uid 500); 5 Feb 2004 09:13:01 -0000 Mailing-List: contact ojb-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "OJB Developers List" Reply-To: "OJB Developers List" Delivered-To: mailing list ojb-dev@db.apache.org Received: (qmail 76941 invoked from network); 5 Feb 2004 09:13:01 -0000 Received: from unknown (HELO relay4.clb.oleane.net) (213.56.31.24) by daedalus.apache.org with SMTP; 5 Feb 2004 09:13:01 -0000 Received: from nodulix ([81.80.231.9]) by relay4.clb.oleane.net with SMTP id i159DAhU003273 for ; Thu, 5 Feb 2004 10:13:12 +0100 From: "Guillaume Nodet" To: "OJB Developers List" Subject: Optimization when storing new objects Date: Thu, 5 Feb 2004 10:13:11 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) In-Reply-To: <40216146.5010002@gmx.ch> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Importance: Normal X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N 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