Postgres Pro
Downloads
Home   >   mailing lists

Re: Naming conventions for lots of stored procedures - Mailing list pgsql-general

From Gerhard Heift
Subject Re: Naming conventions for lots of stored procedures
Date
Msg-id 20100311165315.GB1767@gheift.kawo1.rwth-aachen.de
Whole thread Raw
In response to Re: Naming conventions for lots of stored procedures  (Chris Travers <chris@metatrontech.com>)
Responses Re: Naming conventions for lots of stored procedures  (Pavel Stehule <pavel.stehule@gmail.com>)
List pgsql-general
Tree view 
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
Attachment

pgsql-general by date:

Previous
From: Greg Smith
Date:
Subject: Re: log_statement and syslog severity
Next
From: Ozz Nixon
Date:
Subject: Small install (w/ pSQLODBC support) needed.