Search Postgresql Archives

Naming conventions for lots of stored procedures

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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

-- 
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux