Re: Oracle Closed World
From: Robert Klemme <shortcutter_at_googlemail.com>
Date: Sun, 24 Jun 2012 20:28:10 +0200
Message-ID: <a4p4huFkv7U1_at_mid.individual.net>
On 24.06.2012 19:41, Gerard H. Pille wrote:
> Robert Klemme wrote:
>>
>> It's not the worst thing to motivate developers to move from
>> procedural code to SQL... :-)
>> Procedural is often used because it is easier to understand for
>> humans. But unfortunately you
>> can bring any database's performance down with the wrong set of
>> procedures and triggers.
>
> Not with SQL?
Date: Sun, 24 Jun 2012 20:28:10 +0200
Message-ID: <a4p4huFkv7U1_at_mid.individual.net>
On 24.06.2012 19:41, Gerard H. Pille wrote:
> Robert Klemme wrote:
>>
>> It's not the worst thing to motivate developers to move from
>> procedural code to SQL... :-)
>> Procedural is often used because it is easier to understand for
>> humans. But unfortunately you
>> can bring any database's performance down with the wrong set of
>> procedures and triggers.
>
> Not with SQL?
No, never!! ;-)
My badly worded point was that a procedural solution often cannot be optimized the same way a single query can - for example because the query then is spread across a number of different queries. Or data is aggregated in a temp table and then processed further which creates more IO etc.
Cheers
robert
-- remember.guy do |as, often| as.you_can - without end http://blog.rubybestpractices.com/Received on Sun Jun 24 2012 - 13:28:10 CDT