Re: Naming conventions for lots of stored procedures

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