You are viewing a plain text version of this content. The canonical link for it is here.
Posted to torque-dev@db.apache.org by Robert Dietrick <rd...@sega.com> on 2003/10/09 01:51:44 UTC
village classes doing select before update
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)?
Thanks.
-rob
---------------------------------------------------------------------
To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org
Re: village classes doing select before update
Posted by "Henning P. Schmiedehausen" <hp...@intermeta.de>.
Robert Dietrick <rd...@sega.com> writes:
>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)?
Rip out Village from Torque. However this isn't done in twenty minutes.
Regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
hps@intermeta.de +49 9131 50 654 0 http://www.intermeta.de/
Java, perl, Solaris, Linux, xSP Consulting, Web Services
freelance consultant -- Jakarta Turbine Development -- hero for hire
"Dominate!! Dominate!! Eat your young and aggregate! I have grotty silicon!"
-- AOL CD when played backwards (User Friendly - 200-10-15)
---------------------------------------------------------------------
To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org
Re: village classes doing select before update
Posted by "Daniel L. Rall" <dl...@finemaltcoding.com>.
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