From: Greg Stark <gsstark@mit.edu>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Greg Stark <gsstark@mit.edu>
Cc: Bret Hughes <bhughes@elevating.com>
Cc: Stephan Szabo <sszabo@megazone.bigpanda.com>
Cc: postgresql sql list <pgsql-sql@postgresql.org>
Subject: Re: trigger/for key help
Date: 13 Apr 2004 13:36:01 -0400
Message-ID: <87wu4jdblq.fsf@stark.xeocode.com> (raw)
In-Reply-To: <21878.1081862704@sss.pgh.pa.us>
References: <1081662204.6609.72.camel@bretsony>
<20040411080932.Q83278@megazone.bigpanda.com>
<1081711155.6399.165.camel@bretsony>
<17189.1081720813@sss.pgh.pa.us>
<1081724318.2628.20.camel@bretsony>
<28212.1081736841@sss.pgh.pa.us>
<873c78e6wf.fsf@stark.xeocode.com>
<21878.1081862704@sss.pgh.pa.us>
Tom Lane <tgl@sss.pgh.pa.us> writes:
> Greg Stark <gsstark@mit.edu> writes:
> > Is there a reason postgres goes out of its way to pick names that
> > will be harder to work with than necessary?
>
> If we use ordinary identifiers for system-generated names then we will
> be infringing on user name space --- ie, there's a potential for
> conflict. I suppose we could use long randomly-generated names like
> ewjncm343cnlen, but are those really easier to work with?
I don't see an unseverable link between "user name space" and "identifiers
that don't need to be quoted". Mixed case names for instance seem like
perfectly good user name space identifiers.
Postgres could just as easily say "the system reserves all identifiers
starting with $" and still not require quoting $.
> I think a more useful approach is to treat it as a documentation
> problem. Perhaps an example in the ALTER TABLE man page would help.
--
greg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: gsstark@mit.edu, tgl@sss.pgh.pa.us, bhughes@elevating.com, sszabo@megazone.bigpanda.com
Subject: Re: trigger/for key help
In-Reply-To: <87wu4jdblq.fsf@stark.xeocode.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox