Return-Path: Delivered-To: apmail-db-torque-user-archive@www.apache.org Received: (qmail 33939 invoked from network); 13 Mar 2008 10:25:18 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 13 Mar 2008 10:25:18 -0000 Received: (qmail 75077 invoked by uid 500); 13 Mar 2008 10:25:15 -0000 Delivered-To: apmail-db-torque-user-archive@db.apache.org Received: (qmail 75055 invoked by uid 500); 13 Mar 2008 10:25:14 -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 75044 invoked by uid 99); 13 Mar 2008 10:25:14 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 13 Mar 2008 03:25:14 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [217.24.207.26] (HELO mail.seitenbau.net) (217.24.207.26) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 13 Mar 2008 10:24:37 +0000 Received: from [192.168.15.18] (helo=www.seitenbau.net) by router.seitenbau.net with esmtp (Exim 4.43) id 1JZkcB-0000rU-0h for torque-user@db.apache.org; Thu, 13 Mar 2008 11:24:47 +0100 In-Reply-To: <1204929297.3478.4.camel@raul.n-gage.com> Subject: RE: Can LargeSelect use prepared statements? To: "Apache Torque Users List" X-Mailer: Lotus Notes Release 7.0.1 January 17, 2006 Message-ID: From: Thomas Fischer Date: Thu, 13 Mar 2008 11:24:45 +0100 X-MIMETrack: Serialize by Router on www/seitenbau(Release 7.0.1|January 17, 2006) at 13.03.2008 11:24:46 AM MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII X-Spam-Score: -1.4 (-) X-Spam-Report: -1.4 ALL_TRUSTED Passed through trusted hosts only via SMTP X-Virus-Checked: Checked by ClamAV on apache.org > It looks like Torque's LargeSelect does not use prepared statements in > its queries. Is there a way to make it do that? You would have to modify the Torque code. The problem with using prepared statements is that the Code for creating prepared statements and the code which produces "normal" selects is different, and can produce different outcome for more complicated queries. So with the current code base, having a "switch" is a bad idea because queries could behave differently. Thomas --------------------------------------------------------------------- To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org For additional commands, e-mail: torque-user-help@db.apache.org