Return-Path: Mailing-List: contact torque-user-help@db.apache.org; run by ezmlm Delivered-To: mailing list torque-user@db.apache.org Received: (qmail 27782 invoked from network); 4 Jun 2003 09:00:49 -0000 Received: from unknown (HELO soleri.t-systems.fr) (195.101.57.97) by daedalus.apache.org with SMTP; 4 Jun 2003 09:00:49 -0000 Received: from Paris3.soleri.com ([172.16.98.42]) by soleri.t-systems.fr (Lotus Domino Release 5.0.3 (Intl)) with ESMTP id 2003060411011190:606 ; Wed, 4 Jun 2003 11:01:11 +0200 Received: from imamail.soleri.com ([172.16.102.200]) by Paris3.soleri.com (Lotus Domino Release 5.07a) with ESMTP id 2003060410490974:236 ; Wed, 4 Jun 2003 10:49:09 +0200 Received: from CARAMEL3 ([172.16.102.163]) by imamail.soleri.com (8.11.2/8.11.2) with ESMTP id h548x8g32522 for ; Wed, 4 Jun 2003 10:59:19 +0200 Reply-To: From: "svallet" To: "Turbine Torque Users List" Subject: Strange values in id table Date: Wed, 4 Jun 2003 11:02:21 +0200 Message-ID: MIME-Version: 1.0 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-MIMETrack: Itemize by SMTP Server on Paris3.soleri.com/Soleri(Release 5.07a |May 14, 2001) at 04/06/2003 10:49:09, Serialize by Router on Paris3.soleri.com/Soleri(Release 5.07a |May 14, 2001) at 04/06/2003 10:49:13, Serialize complete at 04/06/2003 10:49:13, Itemize by SMTP Server on Paris1.soleri.com/Soleri(Release 5.0.3 (Intl)|21 March 2000) at 04/06/2003 11:01:12, Serialize by Router on Paris1.soleri.com/Soleri(Release 5.0.3 (Intl)|21 March 2000) at 04/06/2003 11:01:15, Serialize complete at 04/06/2003 11:01:15 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="iso-8859-1" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Hi ! I'm using the id broker feature of Torque ; by looking closer at the id table, I get (what seems to me) very strange results : mysql> select * from id_table; +-------------+-----------------+---------+----------+ | ID_TABLE_ID | TABLE_NAME | NEXT_ID | QUANTITY | +-------------+-----------------+---------+----------+ | 1 | ID_TABLE | 16558 | 713 | | 2 | TYPE_ENTREE | 14251 | 610 | | 3 | ATTRIBUT | 51901 | 2250 | | 4 | DICTIONNAIRE | 1 | 10 | | 5 | NOM_ATTRIBUT | 1 | 10 | | 6 | NOM_TYPE_ENTREE | 1 | 10 | | 7 | LANGUE | 3 | 10 | | 8 | ADOPTION | 61 | 10 | | 29 | SIMON | 31 | 10 | | 89 | T_TEST2 | 1 | 10 | | 139 | T_HELLO | 201 | 10 | | 15132 | T_CUSTOM | 1 | 5 | +-------------+-----------------+---------+----------+ 12 rows in set (0.24 sec) How does it come that Quantity values are so high (2250) ?? my settings are the following (I use torque directly from API) : [some settings] torqueProps.addProperty("torque.idbroker.cleverquantity", "true"); //torqueProps.addProperty("torque.idbroker.prefetch", "false"); //torqueProps.addProperty("torque.idbroker.usenewconnection", "false"); Torque.init(torqueProps); Trying to set "torque.idbroker.prefetch=false" did reset some "Next_id" values to 1, and not some others... so I commented it out ; "usenewconnection" has alwas been uncommented I initialize the id table manually with Quantity values of 10 (the last table is a test case) -> I would _love_ to get Torque to initialize it, but didn't got it right :( (but things seem to work, apart from this) Thanks for any suggestions, Simon -- Simon Vallet T-Systems e-technologies svallet@t-systems.fr