| From: | Curt Sampson <cjs(at)cynic(dot)net> |
|---|---|
| To: | Zeugswetter Andreas SB SD <ZeugswetterA(at)spardat(dot)at> |
| Cc: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: More DROP COLUMN |
| Date: | 2002-07-15 10:35:59 |
| Message-ID: | Pine.NEB.4.44.0207151933180.497-100000@angelic.cynic.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, 15 Jul 2002, Zeugswetter Andreas SB SD wrote:
> I would prefer a simple but highly predictable rule, where you can say
> "Don't name your columns starting with " \353\010" (blank, greek d,
> BS) over some random algo that stays out of the way by means of low
> probability.
\353 is not a delta in most of the character encodings that I use,
and is not valid at all in ASCII. Non-graphic chars are also likely
to cause misery because it's not obvious, using normal tools, what
they are. (The above example would appear to many people as just
a space.)
I would suggest it's probably a good idea to stick to ASCII graphic
(i.e., non-control, not delete) characters.
cjs
--
Curt Sampson <cjs(at)cynic(dot)net> +81 90 7737 2974 http://www.netbsd.org
Don't you know, in this new Dark Age, we're all light. --XTC
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hannu Krosing | 2002-07-15 10:46:40 | advice for user column named cmin |
| Previous Message | Hannu Krosing | 2002-07-15 10:17:11 | Re: More DROP COLUMN |