From torque-dev-return-3594-apmail-db-torque-dev-archive=db.apache.org@db.apache.org Sat Oct 25 03:09:34 2003 Return-Path: Delivered-To: apmail-db-torque-dev-archive@www.apache.org Received: (qmail 71054 invoked from network); 25 Oct 2003 03:09:34 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 25 Oct 2003 03:09:34 -0000 Received: (qmail 67524 invoked by uid 500); 25 Oct 2003 03:09:14 -0000 Delivered-To: apmail-db-torque-dev-archive@db.apache.org Received: (qmail 67515 invoked by uid 500); 25 Oct 2003 03:09:14 -0000 Mailing-List: contact torque-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Apache Torque Developers List" Reply-To: "Apache Torque Developers List" Delivered-To: mailing list torque-dev@db.apache.org Received: (qmail 67502 invoked from network); 25 Oct 2003 03:09:13 -0000 Received: from unknown (HELO drac) (216.27.176.145) by daedalus.apache.org with SMTP; 25 Oct 2003 03:09:13 -0000 Received: from despot (unknown [192.168.1.2]) by drac (Postfix) with ESMTP id 05CE4EAA1 for ; Fri, 24 Oct 2003 23:09:27 -0400 (EDT) Received: from finemaltcoding.com (localhost [127.0.0.1]) by despot (Postfix) with ESMTP id B767D348043 for ; Fri, 24 Oct 2003 20:09:24 -0700 (PDT) Message-ID: <3F99E964.8030608@finemaltcoding.com> Date: Fri, 24 Oct 2003 20:09:24 -0700 From: "Daniel L. Rall" Organization: "Fine Malt Coding" User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030701 X-Accept-Language: en-us, en, es, ja, de-de, zh-cn MIME-Version: 1.0 To: Apache Torque Developers List Subject: Re: village classes doing select before update References: <3F84A310.5080209@sega.com> In-Reply-To: <3F84A310.5080209@sega.com> 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 Robert Dietrick wrote: > I've discovered that the village classes are doing tons of select > statements every time I issue an update on an object. This seems wholly > unnecessary, and it's got my DBA barking down my throat about Oracle > latches and the statement compilation rate skyrocketing. I've seen > references to this problem on the dev list, but I haven't noticed > anything in the changelogs to suggest that it was ever officially fixed > in a later release (I'm using 3.0). Has anyone got any suggestions > about how to either do away with these select statements or force them > to be issued as PreparedStatements instead of Statements (to cut down on > Oracle compiling the statement anew each time)? What version of Village are you using? It used to run a query to get the schema information. In later versions, this meta data is cached. --------------------------------------------------------------------- To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org For additional commands, e-mail: torque-dev-help@db.apache.org