Re: How to tune SQL to avoid ORA-03232 ?

Thanks for the suggestion on "Tools -> Options", but I'd tried it, and it doesn't work any more.

Not sure that Unix is always a benefit - I like my HP, but I've got to install a patch to fix a problem with memory management that crashes PX slaves in 9.2: so I have to download and apply 7 support patches, and five of them are going to do an automatic reboot after install.

I don't think we have any grounds for disagreeing - but I'd argue that my example was exactly to the point. It was three different ways in which three different people might work out and describe their relationship to a specific group of there relatives. All three options were logical - but at implementation time which should I use, the one that is very simple but very inefficient, the one that is very efficient but requires expert knowledge, or the one that it efficient and comprehensible. My case is only that at some point the extra performance benefit may not automatically be worth the risk of complexity.

I think your most important point, though, is the one about row-processing. Thinking non-procedurally is (as your ear-comment indicate) not a human instinct. Mathematical appreciation is something that most people have to be taught very carefully. Since SQL is based on a pure maths model, it isn't surprising that few people end up with an intuitive grasp of how to 'think in SQL' and use it effectively.

--
Regards

Jonathan Lewis
http://www.jlcomp.demon.co.uk

Next Seminar dates:
(see http://www.jlcomp.demon.co.uk/seminar.html )



____USA__________November 7/9   (Detroit)

____USA__________November 19/21 (Dallas)

____England______November 12/14


The Co-operative Oracle Users' FAQ
http://www.jlcomp.demon.co.uk/faq/ind_faq.html



Billy Verreynne wrote in message ...

Part of the problem I think is that many users (and unfortunately,
developers too) view data processing using RDBMS as row processing and
not
data set processing. Oracle is not an ISAM file. Nor is it MS Access
or
dBASE where there is no db engine that can do the data crunching for
you.