And I thought I had this solved.

From: stan <stanb(at)panix(dot)com>
To: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: And I thought I had this solved.
Date: 2019-11-22 23:52:16
Message-ID: 20191122235216.GA7008@panix.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

A while back I ran into problems caused by security fix related to the
search path. I wound up adding a line to. for instance, this function:

REATE FUNCTION
work_hours
(
start_date date,
end_date date
)
RETURNS decimal(10,4) stable
language sql as $$

/* workaround for secuirty "feature" */
SET search_path TO ica, "user" , public;

SELECT
sum(case when
extract(isodow from d)
between 1 and 5 then
8.0 else
+0.0 end)
from

generate_series($1,
$2, interval
'24 hours') d;

$$;

And walked away happy, or so I thought. Now I just got this error:

[local] stan(at)stan=# select * from ttl_avail_hours_by_project_and_employee ;
ERROR: SET is not allowed in a non-volatile function
CONTEXT: SQL function "work_hours" during startup

How can I solve this issue?

--
"They that would give up essential liberty for temporary safety deserve
neither liberty nor safety."
-- Benjamin Franklin

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2019-11-22 23:58:59 Re: And I thought I had this solved.
Previous Message Adrian Klaver 2019-11-22 22:48:50 Re: automated 'discovery' of a table : potential primary key, columns functional dependencies ...