Project

General

Profile

Feature #10142

« Previous | Next »

allow UDFs to live in the public schema instead a UDF-specific schema

Added by Eric Faulhaber about 1 year ago. Updated about 1 year ago.

Status:
New
Priority:
Low
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:

0%

billable:
No
vendor_id:
GCD
case_num:
version_reported:
version_resolved:
reviewer:
production:
No
env_name:
topics:

History

#2 Updated by Eric Faulhaber about 1 year ago

  • Priority changed from Normal to Low

A customer using PostgreSQL in the cloud requested that the native SQL UDFs representing Progress built-in functions be loaded into the public schema rather than the dedicated udf schema. This would avoid the need to have admin/owner access to the target database, which is needed to run the ALTER DATABASE ... SET search_path TO public,udf; command to ensure the udf schema is in the search_path.

Considerations:

  • What analogs (if any) are there to this which need to be considered for other supported database implementations?
  • Upgrading the UDFs (which is necessary from time to time) will be messier, since we cannot simply drop the udf schema to remove the old versions of the UDFs. Existing UDFs will need to be removed/replaced more deliberately.

Also available in: Atom PDF