Return-Path: Mailing-List: contact ojb-dev-help@db.apache.org; run by ezmlm Delivered-To: mailing list ojb-dev@db.apache.org Received: (qmail 1677 invoked from network); 6 Apr 2003 18:08:44 -0000 Received: from mailout05.sul.t-online.com (194.25.134.82) by daedalus.apache.org with SMTP; 6 Apr 2003 18:08:44 -0000 Received: from fwd03.sul.t-online.de by mailout05.sul.t-online.com with smtp id 192EZT-0001Uz-01; Sun, 06 Apr 2003 20:08:47 +0200 Received: from win (510007636964-0001@[80.145.84.53]) by fmrl03.sul.t-online.com with smtp id 192EZ8-0E1lh2C; Sun, 6 Apr 2003 20:08:26 +0200 Message-ID: <061d01c2fc67$83612cd0$6479fea9@win> Reply-To: "Armin Waibel" From: "Armin Waibel" To: "OJB Developers List" References: <20030406172644.60717.qmail@icarus.apache.org> Subject: Re: cvs commit: db-ojb/src/java/org/apache/ojb/broker/accesslayer ConnectionManagerImpl.java Date: Sun, 6 Apr 2003 20:08:23 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 X-Sender: 510007636964-0001@t-dialin.net X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Hi Oleg, there are some user (one I remember ;-)) who proposed to let this 'hack' be normal behaviour. Then it is a) possible to write code using batch updates with the PB-api and b) if you don't want to use it, easy to completely switch off without source changes Currently it is not possible, if your database supports batch updates, NOT to use this feature in ODMG (or PB level if batch is set true). What are the arguments against such a behaviour? regards, Armin ----- Original Message ----- From: To: Sent: Sunday, April 06, 2003 7:26 PM Subject: cvs commit: db-ojb/src/java/org/apache/ojb/broker/accesslayer ConnectionManagerImpl.java > olegnitz 2003/04/06 10:26:44 > > Modified: src/java/org/apache/ojb/broker/accesslayer > ConnectionManagerImpl.java > Log: > Batch mode for ODMG turned on back since all known problems are solved > > Revision Changes Path > 1.5 +2 -11 db-ojb/src/java/org/apache/ojb/broker/accesslayer/ConnectionManagerImpl. java > > Index: ConnectionManagerImpl.java > =================================================================== > RCS file: /home/cvs/db-ojb/src/java/org/apache/ojb/broker/accesslayer/ConnectionMa nagerImpl.java,v > retrieving revision 1.4 > retrieving revision 1.5 > diff -u -r1.4 -r1.5 > --- ConnectionManagerImpl.java 20 Mar 2003 19:13:55 -0000 1.4 > +++ ConnectionManagerImpl.java 6 Apr 2003 17:26:44 -0000 1.5 > @@ -307,16 +307,7 @@ > */ > public void setBatchMode(boolean mode) > { > - /* > - arminw: > - HACK, > - only enable batch-mode when user set attribute > - 'true' till problem with batch-mode are solved. > - This allows user to set batch mode 'true' in code > - but give full control via configuration file 'batch-mode' > - attribute. > - */ > - batchMode = mode && jcd.getBatchMode(); > + batchMode = mode; > } > > /** > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org > For additional commands, e-mail: ojb-dev-help@db.apache.org > > >