Creating Functions in a Separate Schema - Mailing list pgsql-novice

From Mark Dexter
Subject Creating Functions in a Separate Schema
Date
Msg-id 5E8F9F5B63726C48836757FE673B584EF747B4@dcimail.dexterchaney.local
Whole thread Raw
List pgsql-novice

Our application currently runs in SQL Server and we are porting it over to Postgres.  When we write enbedded SQL queries for SQL Server, we need to reference user-defined functions with the prefix "dbo." (e.g., "dbo.Function_Name()").  In experimenting with Postgres, it appears that we can create a schema called "dbo" and then reference functions with the same syntax (e.g., "dbo.Function_Name()"). 

We're trying to understand whether there will be any disadvantages to doing this.  One issue we have discovered is that any public table or view references in these functions need to explicitly use the "public." prefix for the tables or views.  Are there any other issues or problems with this approach?  Any help will be greatly appreciated.  Thanks. 

pgsql-novice by date:

Previous
From: Steve Crawford
Date:
Subject: Re: MySQL vs PostgreSQL
Next
From: Frank Kurzawa
Date:
Subject: Trying to find a renegade lock