Re: Naming conventions for lots of stored procedures

From: Gerhard Heift <ml-postgresql-20081012-3518(at)gheift(dot)de>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Naming conventions for lots of stored procedures
Date: 2010-03-11 16:53:15
Message-ID: 20100311165315.GB1767@gheift.kawo1.rwth-aachen.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, Mar 11, 2010 at 08:38:46AM -0800, Chris Travers wrote:
> > On 3/10/2010 11:52 PM, Chris Travers wrote:
> > Which
> > i'm at a loss why nesting would help solve any problem what so ever. I
> > imagine the search path on some connections would be all inclusive so
> > ambiguous names is not solved. Also would not be a big fan typing
> > something like
> >
> > AR.Customer.Editing.Delete(ID)

Why dont you create such a function if you need it?

CREATE FUNCTION "AR.Customer.Editing.Delete"(integer) ...

Regards,
Gerhard

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Greg Smith 2010-03-11 17:06:39 Re: log_statement and syslog severity
Previous Message Chris Travers 2010-03-11 16:38:46 Re: Naming conventions for lots of stored procedures