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 56790 invoked from network); 1 Apr 2003 14:18:46 -0000 Received: from mailout03.sul.t-online.com (194.25.134.81) by daedalus.apache.org with SMTP; 1 Apr 2003 14:18:46 -0000 Received: from fwd01.sul.t-online.de by mailout03.sul.t-online.com with smtp id 190Mb6-00036P-0A; Tue, 01 Apr 2003 16:18:44 +0200 Received: from win (510007636964-0001@[80.145.82.24]) by fmrl01.sul.t-online.com with smtp id 190Mau-1NzuJUC; Tue, 1 Apr 2003 16:18:32 +0200 Message-ID: <007701c2f859$8fcc8bc0$6479fea9@win> Reply-To: "Armin Waibel" From: "Armin Waibel" To: "OJB Users List" , "OJB Developers List" Subject: [CVS sequence package] SequenceManagerHighLowImpl changed Date: Tue, 1 Apr 2003 16:18:25 +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 all, currently I checked in a new version of SequenceManagerHighLowImpl. Now the implementation use otimistic locking to avoid id generation problems when OJB was used in different JVM with same database. To enable this behaviour the OJB_HL_SEQ table was enhanced. The table needs an additional INTEGER column VERSION. If you want to update drop OJB_HL_SEQ table and recreate it with the new field. regards, Armin