db-torque-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bogdan Vatkov" <bvat...@globaltech-bg.com>
Subject Re: IDBroker broken ?
Date Thu, 11 Dec 2003 10:03:31 GMT
Hi Siegfried,

This is not reproducable in means of exact ID ..but i could say when i run
the 1,000,000 cycle
I never reach 100,000 successfully.
I suppose the problem could be in the mysql server.
I think that jdbc transactions mechanism has nothing to do with the SQL
creation script for a particular DB
but is sensible of the possibility of the db server to support transactions
at all or i am wrong ?

With best regards,
Bogdan
----- Original Message -----
From: "Göschl,Siegfried" <Siegfried.Goeschl@drei.com>
To: "Apache Torque Users List" <torque-user@db.apache.org>
Sent: Thursday, December 11, 2003 11:06
Subject: RE: IDBroker broken ?


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= IDBroker

Usualy it works just fine ..but the following test fails somewhen:

            /*   MASS TEST */
            for (int i=0;i<1000000;i++) {
              User temp = 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.
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



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


Mime
View raw message