From torque-user-return-3194-apmail-db-torque-user-archive=db.apache.org@db.apache.org Wed Oct 08 18:46:02 2003 Return-Path: Delivered-To: apmail-db-torque-user-archive@www.apache.org Received: (qmail 22973 invoked from network); 8 Oct 2003 18:46:01 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 8 Oct 2003 18:46:01 -0000 Received: (qmail 92829 invoked by uid 500); 8 Oct 2003 18:45:49 -0000 Delivered-To: apmail-db-torque-user-archive@db.apache.org Received: (qmail 92759 invoked by uid 500); 8 Oct 2003 18:45:48 -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 92743 invoked from network); 8 Oct 2003 18:45:48 -0000 Received: from unknown (HELO mail.sega.com) (64.95.120.84) by daedalus.apache.org with SMTP; 8 Oct 2003 18:45:48 -0000 Received: from sega.com (dhcp-10-10-10-30.sega.com [10.10.10.30]) by mail.sega.com (Mirapoint Messaging Server MOS 3.3.6-GR) with ESMTP id AHG99311; Wed, 8 Oct 2003 11:45:52 -0700 (PDT) Message-ID: <3F845A83.8020208@sega.com> Date: Wed, 08 Oct 2003 11:42:11 -0700 From: Robert Dietrick Reply-To: robd@sega.com User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2) Gecko/20021126 X-Accept-Language: en-us, en, pt-br MIME-Version: 1.0 To: torque-user@db.apache.org Subject: oracle statement parsing/select * from ... Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N I'm using Torque 3.0, and I've modified all of the generated code to make doPSSelect() calls instead of doSelect() calls. Still, our DBA insists that he sees a high parse rate in our Oracle database with statements such as: SELECT * FROM user_action WHERE USER_ID=51521 I've seen references in the mailing list archives to problems in which Torque does a select before issuing an update or insert statement. Can anyone shed any light on this situation? Has anyone else encountered this? -rob --------------------------------------------------------------------- To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org For additional commands, e-mail: torque-user-help@db.apache.org