Re: Oracle Closed World
From: Gerard H. Pille <ghp_at_skynet.be>
Date: Sun, 24 Jun 2012 21:14:22 +0200
Message-ID: <4fe766ee$0$3104$ba620e4c_at_news.skynet.be>
Robert Klemme wrote:
> 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.
>
Date: Sun, 24 Jun 2012 21:14:22 +0200
Message-ID: <4fe766ee$0$3104$ba620e4c_at_news.skynet.be>
Robert Klemme wrote:
> 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.
>
I know, Robert, I know, just kidding. I know people who'd call two functions to retrieve two columns from the same record. Received on Sun Jun 24 2012 - 14:14:22 CDT