Received: from candle.pha.pa.us (maillist@s5-03.ppp.op.net [209.152.195.67]) by hub.org (8.9.3/8.9.3) with ESMTP id NAA36155; Mon, 11 Oct 1999 13:05:43 -0400 (EDT) (envelope-from maillist@candle.pha.pa.us) Received: (from maillist@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id NAA05891; Mon, 11 Oct 1999 13:04:56 -0400 (EDT) From: Bruce Momjian Message-Id: <199910111704.NAA05891@candle.pha.pa.us> Subject: Re: [HACKERS] Re: [INTERFACES] Next release is 7.0(?) In-Reply-To: <199910111656.KAA17620@biology.nmsu.edu> from Brook Milligan at "Oct 11, 1999 10:56:30 am" To: Brook Milligan Date: Mon, 11 Oct 1999 13:04:56 -0400 (EDT) CC: lockhart@alumni.caltech.edu, ser@perio.unlp.edu.ar, pgsql-hackers@postgreSQL.org, pgsql-interfaces@postgreSQL.org X-Mailer: ELM [version 2.4ME+ PL56 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit > > I hope we don't have a consensus on this. Long commands with > > underscores in them are certainly another sign of the coming > > apocalypse ;) > > But if we keep symlinks to the existing names, is that OK? > > Isn't the point to avoid naming conflicts. Symlinks won't help that, > surely. > > I agree; underscores are a pain. If you must go this direction, I > suggest hyphens (-). You could make the actual command pg_createuser, and make a symlink of createuser, but allow the symlink creation to fail. Best of both worlds, I think. I vote for underscore. That's what I normally use. Dashes look too much like command arguments. -- Bruce Momjian | http://www.op.net/~candle maillist@candle.pha.pa.us | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026