Function 'myfunc' may not be used in SQL Options

Question

<p>
Hello,
I have created a simple function in a packege for use in an update statement. The function is
FUNCTION myfnc(p1 IN t1.c1%TYPE)
RETURN VARCHAR2
IS
BEGIN
IF p1 = 3 THEN
RETURN 'A';
ELSE
RETURN 'B';
END IF;
END myfnc;
I use it in a procedure which exists in the same package as the function as follows
Update t1
set c1 = myfnc(c2);
I am getting the compliation error Function 'myfunc' may not be used in SQL.
There is no db manipulation going on and I have tried using
PRAGMA RESTRICT_REFERENCES (myfnc, WNDS, WNPS, RNDS, RNPS);
but to no avail.
One other thing is that I thought this was compiling OK but then I decided to put the function in the package specification so I could unit test it using a db call. Now if I drop and recreate the package without the declaration in the specification the compile error still occurs. Perhaps that's my mind playing tricks but maybe there is something here I am not aware of.
Any suggestions?
</p>

Answer 1

Hi,
You found the solution.
Although it's allowed to say
Update     t1
set     c1 = local_var;in a package, where local_var is not defined outside of the procedure, let alone the package, and
although it's legal to say:
local_var = myfnc (some_other_var); inside the package where myfnc is a private function (included in the package body, but not in the package header), still
it is not legal to say:
Update     t1
set     c1 = myfnc (c2); If there is a problem with putting myfnc in the package header (for example, you don't want people calling it directly, for some reason), you can make it a stand-alone function, like Someoneelse did, or put in a different package, and give the owner of your first package (and no one else) EXECUTE privileges on it.
As William pointed out, if myfnc is really this simple, you might not need a function at all.