Return-Path: Delivered-To: apmail-db-torque-user-archive@www.apache.org Received: (qmail 16579 invoked from network); 17 Jul 2006 14:02:36 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 17 Jul 2006 14:02:36 -0000 Received: (qmail 33397 invoked by uid 500); 17 Jul 2006 14:02:33 -0000 Delivered-To: apmail-db-torque-user-archive@db.apache.org Received: (qmail 33361 invoked by uid 500); 17 Jul 2006 14:02:33 -0000 Mailing-List: contact torque-user-help@db.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: 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 33329 invoked by uid 99); 17 Jul 2006 14:02:33 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 Jul 2006 07:02:33 -0700 X-ASF-Spam-Status: No, hits=1.4 required=10.0 tests=DNS_FROM_RFC_ABUSE,DNS_FROM_RFC_WHOIS X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Received: from [144.140.92.153] (HELO omta01sl.mx.bigpond.com) (144.140.92.153) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 Jul 2006 07:02:30 -0700 Received: from [127.0.0.1] (really [155.143.101.187]) by omta01sl.mx.bigpond.com with ESMTP id <20060717140207.DGVV3114.omta01sl.mx.bigpond.com@[127.0.0.1]> for ; Mon, 17 Jul 2006 14:02:07 +0000 Message-ID: <44BB973D.1060003@bigpond.net.au> Date: Mon, 17 Jul 2006 23:57:17 +1000 From: Steve Vanspall User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: Apache Torque Users List Subject: Re: IdBroker with sequences in DB2, or perhaps native. How does it work References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus: avast! (VPS 0628-5, 14/07/2006), Outbound message X-Antivirus-Status: Clean X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Ok thanks, so toruqe isn't really the right solution for a pre existing app. I basically was trying to build some tools for a web app that used our own set of persistence objects etc. We made it well before there was anything decent out there. Figured if torque can do it for me for this tools based app, why go through the trouble of separating the cod eI have from the project to make some tools. Oh well thatnks steve Thomas Fischer wrote: > Hi, > > IdBroker is no good for that. It uses an extra table and no sequences. In > native, Torque uses fixed names for the sequences it uses. See the > create-db sql for the names. Maybe you can rename your existing sequence to > fit that name ? > In the postgesql howto, there is also a paragraph about non-fittibg > seqjence names. However, I do not know whether the solution outlined there > is good for db2 and whether it still works. > > Thomas > > Steve Vanspall schrieb am 15.07.2006 08:53:38: > > >> Hi there, >> >> I am going mad here. >> >> I have tried a few options for geting torque to use an already existing >> sequence , in db2, to generate the id's for certain tables. >> >> One article suggested setting the defaultIdMethod to native and having a >> parameter "id-method-parameter" whose vlaue is the name of the sequence >> to be used. >> >> This doesnt work, all I get is. >> >> this warning >> >> IDBroker - IDBroker is being used with db '@DB_NAME@', which does not >> support transactions. IDBroker attempts to use transactions to limit the >> possibility of duplicate key generation. Without transactions, >> duplicate key generation is possible if multiple JVMs are used or other >> means are used to write to the database. >> >> follow by the following exception >> >> There was no DataSourceFactory configured for the connection @DB_NAME@ >> >> So I tried setting the dafultIdMEthod to idbroker. >> >> the same thing happened. >> >> Do I have to define a class that get the sequence data for me. This is >> no problem, but I cannot find any decent documentation stating how to do >> this. >> >> What do I implement and how do I tell torque what class isthe id broker?? >> >> Any help would be appreciated >> >> Steve >> >> --------------------------------------------------------------------- >> 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 > > > --------------------------------------------------------------------- To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org For additional commands, e-mail: torque-user-help@db.apache.org