Naming conventions for lots of stored procedures

From: Chris Travers <chris(at)metatrontech(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Naming conventions for lots of stored procedures
Date: 2010-03-11 01:16:44
Message-ID: 5ed37b141003101716h1e8e4dc8s5749ffd1ec285c7e@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi all;

One of my applications currently has over 60 stored procedures and
future versions will likely have several hundred. I am wondering what
folks find to be helpful naming conventions for managing a large
number of stored procedures. We tried using double underscores to
separate module vs procedure names and that just became a mess. I
have found a few possible separators that might possibly work but they
are aesthetically revolting (_$ for example, like select
test_$echo(1);).

I can't imagine I am the first person to run up against this problem
and would rather ask advice of more experienced folks then to wander
from one maintenance headache into a possibly far worse one.

So, what are approaches each of you have taken in the past?

Best Wishes,
Chris Travers

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Bruce Momjian 2010-03-11 01:42:59 Re: log_statement and syslog severity
Previous Message Amol Chiplunkar 2010-03-11 00:00:00 crosstab functionality for postgres 8.1.4