db-torque-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel L. Rall" <...@finemaltcoding.com>
Subject Re: village classes doing select before update
Date Sat, 25 Oct 2003 03:09:24 GMT
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


Mime
View raw message