Return-Path: Delivered-To: apmail-db-torque-user-archive@www.apache.org Received: (qmail 23373 invoked from network); 14 Mar 2005 16:06:55 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 14 Mar 2005 16:06:55 -0000 Received: (qmail 62008 invoked by uid 500); 14 Mar 2005 16:06:53 -0000 Delivered-To: apmail-db-torque-user-archive@db.apache.org Received: (qmail 61991 invoked by uid 500); 14 Mar 2005 16:06:53 -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 61978 invoked by uid 99); 14 Mar 2005 16:06:53 -0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS X-Spam-Check-By: apache.org Received-SPF: neutral (hermes.apache.org: local policy) Received: from moutng.kundenserver.de (HELO moutng.kundenserver.de) (212.227.126.185) by apache.org (qpsmtpd/0.28) with ESMTP; Mon, 14 Mar 2005 08:06:51 -0800 Received: from [212.227.126.205] (helo=mrelayng.kundenserver.de) by moutng.kundenserver.de with esmtp (Exim 3.35 #1) id 1DAs5g-000286-00 for torque-user@db.apache.org; Mon, 14 Mar 2005 17:06:48 +0100 Received: from [217.7.104.70] (helo=ex1.GT.local) by mrelayng.kundenserver.de with asmtp (Exim 3.35 #1) id 1DAs5g-0000P4-02 for torque-user@db.apache.org; Mon, 14 Mar 2005 17:06:48 +0100 Received: from m-ex1.GT.local ([192.168.100.12]) by ex1.GT.local with Microsoft SMTPSVC(5.0.2195.5329); Mon, 14 Mar 2005 17:04:15 +0100 Content-class: urn:content-classes:message Subject: AW: inefficient doDelete MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Mon, 14 Mar 2005 17:04:11 +0100 Message-ID: <5EE5137D79A3CA45970354F512B3F3E304E7CD@m-ex1.gt.local> X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: inefficient doDelete Thread-Index: AcUorNuQP0kM8jJhSiqGnN8a4wJk3gAAfG2w From: "Vitzethum, Daniel" To: "Apache Torque Users List" X-OriginalArrivalTime: 14 Mar 2005 16:04:16.0343 (UTC) FILETIME=[78F1D670:01C528AF] X-Provags-ID: kundenserver.de abuse@kundenserver.de auth:08b64d493f559a3060db53eba29a9aeb X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Hello, Paul was asking how people are handling the situation. Well, this seems by now to be the only possible way for Paul to get his things done. I do not disregard usage of Torque, rather than using it myself, but was just answering Paul's question. As you may have mentioned, I use Torque's constants for TABLE_NAME and columns to mimimize the risks you are talking of. Surely this is a pragmatic approach - please notice I was answering as a Torque user, not a Torque developer. Daniel --------------------------------------------------------------------- To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org For additional commands, e-mail: torque-user-help@db.apache.org