I’ve always used schemas – usually one for each of the business processes.
From: pgsql-general-owner@postgresql.org [mailto:pgsql-general-owner@postgresql.org] On Behalf Of Pavel Stehule
Sent: Thursday, March 19, 2015 12:38 AM
To: Tim Uckun
Cc: pgsql-general
Subject: Re: [GENERAL] Name spacing functions and stored procedures
Hi
2015-03-19 2:56 GMT+01:00 Tim Uckun <timuckun@gmail.com>:
What do you guys do to namespace your functions so that they are not jumbled in with the system functions and also somewhat hierarchically organized.
Obviously it's possible to create schemas for different namespaces but that can lead to a lot of schemas which hold no data. The other way is to simply name your functions like _lib_etl_csv_import_weird_data_format but that's not too much fun either.
What is problem with schemas? It is tool for logical database structuring - for tables, for functions.
I use schemas without any problems.
Just curious how other people deal with the issue.
NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.
