[postgis-tickets] r15032 - schema qualify raster function calls

Regina Obe lr at pcorp.us
Fri Aug 5 05:56:02 PDT 2016


No.  Because when you install postgis, they get schema qualified anyway
because it goes where you install, so no need to schema qualify the function
create calls.

The extension one does set search path  internally already.  

The non-extension, I think we should have do set search path once we work
out how we are going to do schema at compile time or have a script for that.
Right now the @extschema@, gets stripped out for non-extension so its
business as usual for non-extension.  

-----Original Message-----
From: strk at kbt.io [mailto:strk at kbt.io] 
Sent: Friday, August 05, 2016 5:44 AM
To: Regina Obe <lr at pcorp.us>
Cc: postgis-tickets at lists.osgeo.org
Subject: Re: [postgis-tickets] r15032 - schema qualify raster function calls

On Sun, Jul 31, 2016 at 10:15:44PM -0700, Regina Obe wrote:

>  CREATE OR REPLACE FUNCTION box3d(raster)
>      RETURNS box3d
> -    AS 'select box3d(st_convexhull($1))'
> +    AS 'select box3d( @extschema at .ST_convexhull($1))'
>      LANGUAGE 'sql' IMMUTABLE STRICT _PARALLEL;

Shouldn't the signature of the function being created also be fully
qualified ? As in:

  CREATE OR REPLACE FUNCTION @extschema at .box3d(raster)

Or does the script (non-extension) start with a "set search_path" ?

--strk;



More information about the postgis-tickets mailing list