Creating Functions in Separate Schema - Mailing list pgsql-general

From Mark Dexter
Subject Creating Functions in Separate Schema
Date
Msg-id 5E8F9F5B63726C48836757FE673B584EF74CB5@dcimail.dexterchaney.local
Whole thread Raw
Responses Re: Creating Functions in Separate Schema  (Tino Wildenhain <tino@wildenhain.de>)
Re: Creating Functions in Separate Schema  (Richard Huxton <dev@archonet.com>)
Re: Creating Functions in Separate Schema  (Oliver Elphick <olly@lfix.co.uk>)
List pgsql-general

Our application currently runs in Microsoft 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.  Are there any possible issues or problems with this approach?  Any help will be greatly appreciated.  Thanks. 

pgsql-general by date:

Previous
From: Greg Stark
Date:
Subject: Re: R: R: space taken by a row & compressed data
Next
From: Gaetano Mendola
Date:
Subject: Re: Possible to insert quoted null value into integer field?