Re: SHow a cursor
From: Gerard H. Pille <ghp_at_skynet.be>
Date: Wed, 08 Feb 2012 21:37:52 +0100
Message-ID: <4f32dd0d$0$5049$ba620e4c_at_news.skynet.be>
Peter Schneider wrote:
> Am 08.02.2012 19:39, schrieb Gerard H. Pille:
>> Tim Slattery wrote:
>>> Tim Slattery<Slattery_T_at_bls.gov> wrote:
>>>
>>>
>>>> The "select" statement works when I run it from the SQL developer
>>>> console. But when I call the function I'm told "table or view does not
>>>> exist". But it *does* exist.
>>>
>>> I saw a web post that may have the answer. He says that a common cause
>>> of this is that select permission on the table has been granted to a
>>> role, and that role has then been assigned (granted? not sure of the
>>> proper terminology) to me. But that role does not propagate to
>>> functions that I write. The result is just what I'm seeing: I can
>>> select from the table directly, but the function can't find it.
>>>
>>> Seems an irrational way for things to work, but then I'm only a
>>> developer...
>>>
>>
>> If you'd like to become a good developer, don't use dynamic SQL.
>
> If you'd like to become a superb developer, learn how to use dynamic SQL at great depth, know
> what bind variables are good for, learn what excessive parsing means to your application
> performance...
>
> And then you learn when dynamic SQL is appropriate and when not.
>
> DBMS_SQL, EXECUTE IMMEDIATE and OPEN ... FOR '...' can do magic in the hand of PL/SQL wizards ;-)
>
> Regards
> Peter
>
Date: Wed, 08 Feb 2012 21:37:52 +0100
Message-ID: <4f32dd0d$0$5049$ba620e4c_at_news.skynet.be>
Peter Schneider wrote:
> Am 08.02.2012 19:39, schrieb Gerard H. Pille:
>> Tim Slattery wrote:
>>> Tim Slattery<Slattery_T_at_bls.gov> wrote:
>>>
>>>
>>>> The "select" statement works when I run it from the SQL developer
>>>> console. But when I call the function I'm told "table or view does not
>>>> exist". But it *does* exist.
>>>
>>> I saw a web post that may have the answer. He says that a common cause
>>> of this is that select permission on the table has been granted to a
>>> role, and that role has then been assigned (granted? not sure of the
>>> proper terminology) to me. But that role does not propagate to
>>> functions that I write. The result is just what I'm seeing: I can
>>> select from the table directly, but the function can't find it.
>>>
>>> Seems an irrational way for things to work, but then I'm only a
>>> developer...
>>>
>>
>> If you'd like to become a good developer, don't use dynamic SQL.
>
> If you'd like to become a superb developer, learn how to use dynamic SQL at great depth, know
> what bind variables are good for, learn what excessive parsing means to your application
> performance...
>
> And then you learn when dynamic SQL is appropriate and when not.
>
> DBMS_SQL, EXECUTE IMMEDIATE and OPEN ... FOR '...' can do magic in the hand of PL/SQL wizards ;-)
>
> Regards
> Peter
>
And bring a production database to its knees. Received on Wed Feb 08 2012 - 14:37:52 CST