Return-Path: Delivered-To: apmail-db-torque-user-archive@www.apache.org Received: (qmail 21783 invoked from network); 11 Dec 2003 09:06:46 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 11 Dec 2003 09:06:46 -0000 Received: (qmail 12582 invoked by uid 500); 11 Dec 2003 09:06:19 -0000 Delivered-To: apmail-db-torque-user-archive@db.apache.org Received: (qmail 12570 invoked by uid 500); 11 Dec 2003 09:06:18 -0000 Mailing-List: contact torque-user-help@db.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Apache Torque Users List" Reply-To: "Apache Torque Users List" Delivered-To: mailing list torque-user@db.apache.org Received: (qmail 12557 invoked from network); 11 Dec 2003 09:06:18 -0000 Received: from unknown (HELO msx.drei.com) (213.94.78.66) by daedalus.apache.org with SMTP; 11 Dec 2003 09:06:18 -0000 Received: from msx.drei.com ([10.249.20.17]) by msx.drei.com with Microsoft SMTPSVC(5.0.2195.6713); Thu, 11 Dec 2003 10:06:30 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: IDBroker broken ? Date: Thu, 11 Dec 2003 10:06:30 +0100 Message-ID: <90B3A0967470D44CB8FDE74907512328F1CDE3@av1s008.at-work.local> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: IDBroker broken ? Thread-Index: AcO/xPxuh0TIFkYJRYmDGFPSfJQEQQAAE7uQ From: =?iso-8859-1?Q?=22G=F6schl=2CSiegfried=22?= To: "Apache Torque Users List" X-OriginalArrivalTime: 11 Dec 2003 09:06:30.0251 (UTC) FILETIME=[10C87BB0:01C3BFC6] 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 Hi Bogdan, +) If you are using transactions or not is defined the SQL script = creating your DB - something such as "USE IMNODB" at the end of the = table definition. +) Is this behaviour reproducable, e.g. always fails for the same ID = generated by the IDBroker?! Cheers, Siegfried Goeschl -----Original Message----- From: Bogdan Vatkov [mailto:bvatkov@globaltech-bg.com] Sent: Thursday, December 11, 2003 9:59 AM To: torque-user@db.apache.org Subject: IDBroker broken ? Hi all, I am using torque with mysql 4.0.13 with IDmethod=3D IDBroker Usualy it works just fine ..but the following test fails somewhen: /* MASS TEST */ for (int i=3D0;i<1000000;i++) { User temp =3D new User(); temp.setLoginName("user"+String.valueOf(i)); temp.setPassword(temp.getLoginName()); temp.save(); } I try to mass generate 1,000,000 User objects into db.=20 but on the 37,416 th iteration mysql jdbc driver says: Duplicate entry for ..bla bla bla .....the id of the table has = duplicated then again on 6x,xxx th iteration...than on again 9x,xxx .. I think that in that version of the mysql server thera are transactions = available (torque does not warn me for an absence of transactional = support for the db, so i believe my server has transactions) I do not want to debug torque's code ..or neither to change it ...could = somebody give me a hint ..what may be the reason leading to this? This problem occurs only in this MASS test ...for now ... Thanks in advance Bogdan --------------------------------------------------------------------- To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org For additional commands, e-mail: torque-user-help@db.apache.org