Saga continues ([Zope-DB] DCOracle2: close connection doesn't)

[Dario Lopez-Kästen]

actually, what no app will protect you from is bad sql. What Zope should
protect us from is dropped connections for long running SQL-executes.

In our app, the main reason for long-running queries is because of bad SQL.
We run our Oracle on an Sun 880 with 8 processors. This is a fast machine -
still the app is slow, becasue of the way the queries force the DB to do
stupid things, like iterate thru one table several hundred times just to
retrieve 10 odd rows from it (and this is a real world example, not
something I made up to show as an example).

I can live with Zope waiting for the DB to respond. What I cannot live with
is Zope waiting for a response on a connection that was dropped for some
unknown reason.

Cheers,

/dario

----- Original Message -----
From: "Iain (Jethro) Anderson" <Jethro.Anderson at bristol.ac.uk>
To: "Paul Browning" <paul.browning at bristol.ac.uk>; <zope-db at zope.org>
Cc: "Dieter Maurer" <dieter at handshake.de>
Sent: Thursday, October 02, 2003 10:37 AM
Subject: Re: Saga continues ([Zope-DB] DCOracle2: close connection doesn't)


> Sorry that was really meant for Paul's eyes only :-)
>
> --On Thursday, October 02, 2003 09:14:04 +0100 "Iain (Jethro) Anderson"
> <Jethro.Anderson at bristol.ac.uk> wrote:
>
> > Until yesterday pm - JDBC connections from a development version of
> > personinfo (being run against a production database !!!!) nearly brought
> > HPROD to its knees.
> >
> > --On Thursday, October 02, 2003 01:08:22 +0100 Paul Browning
> > <paul.browning at bristol.ac.uk> wrote:
> >
> > <snip>
> >> I will observe the following: the many Oracle instances are
> >> also used by Java and Perl apps. There have been, I understand,
> >> no problems with database connectivity with the non-Zope apps.
> >>
> > <snip>
> >