Re: More DROP COLUMN - Mailing list pgsql-hackers

From Zeugswetter Andreas SB SD
Subject Re: More DROP COLUMN
Date
Msg-id 46C15C39FEB2C44BA555E356FBCD6FA4961E20@m0114.s-mxs.net
Whole thread Raw
In response to More DROP COLUMN  ("Christopher Kings-Lynne" <chriskl@familyhealth.com.au>)
Responses Re: More DROP COLUMN  (Curt Sampson <cjs@cynic.net>)
List pgsql-hackers
> 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


pgsql-hackers by date:

Previous
From: "Christopher Kings-Lynne"
Date:
Subject: Re: More DROP COLUMN
Next
From: Hannu Krosing
Date:
Subject: Re: More DROP COLUMN