
> However, I'm not happy with the way dropped columns are renamed.  I want to
> give them a name that no-one would ever want to use as a legit column name.
> I don't like this behaviour:

Yes, how about prepending a character that would usually need to be escaped.

I like Hannu's proposal with the blanks " col1 dropped@2002-07-17.10:30:00",
the underscores are too commonly used.
Maybe add two characters, one special and a backspace after the first blank. 
So it would print nicely, but be very unlikely.

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.

Andreas

Mon, 15 Jul 2002 11:10:03 +0200
"Zeugswetter Andreas SB SD" <ZeugswetterA@spardat.at>
Re: More DROP COLUMN
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@cynic.net>   +81 90 7737 2974   http://www.netbsd.org
    Don't you know, in this new Dark Age, we're all light.  --XTC


Mon, 15 Jul 2002 19:35:59 +0900 (JST)
Curt Sampson <cjs@cynic.net>
Re: More DROP COLUMN