2010/3/11 Gerhard Heift <ml-postgresql-20081012-3...@gheift.de>: > 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) ...
it's not good idea. Case sensitive names are usually problem. Customer.Editing.Delete isn't best identifier too - "Editing" is useless. customer_delete is enough. Regards Pavel Stehule > > Regards, > Gerhard > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.10 (GNU/Linux) > > iEYEARECAAYFAkuZH/sACgkQa8fhU24j2fml2gCgkpZfQ53fxotGDBoG4BYgIUZG > 2vUAn19yVUFq6hzAHFN0hAONiydtqq3B > =ZLVm > -----END PGP SIGNATURE----- > > -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
