Re: More DROP COLUMN - Mailing list pgsql-hackers

From Hannu Krosing
Subject Re: More DROP COLUMN
Date
Msg-id 1026728231.29268.10.camel@taru.tm.ee
Whole thread Raw
In response to Re: More DROP COLUMN  ("Christopher Kings-Lynne" <chriskl@familyhealth.com.au>)
Responses Re: More DROP COLUMN  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Mon, 2002-07-15 at 09:20, Christopher Kings-Lynne wrote:
> > > etc.  I put that extra number after dropped and not at the end
> > so prevent it
> > > being off the end of a 32 character name.
> > >
> > > > Alternatively, we could invest a lot of work to make it possible for
> > > > attname to be NULL, but I don't see the payoff...
> > >
> > > Yeah, I think a weird name should be good enough...
> >
> > perhaps starting it with spaces instead of _ would make it even harder
> > to write by accident, so tha name could be
> >    "         dropped 0000000001"
> >
> > or to make it even more self documenting store the drop time,
> > " col001 dropped@020715.101427"
> > --------------------------------
> 
> Well, are there characters that are illegal in column names that I could
> use?  I did a quick check and couldn't find any!

I guess that \0 would be unusable (not sure if its illegal)

\r \n and \t (and others < 0x20) are probably quite unlikely too.

--------------
Hannu



pgsql-hackers by date:

Previous
From: "Zeugswetter Andreas SB SD"
Date:
Subject: Re: More DROP COLUMN
Next
From: Hannu Krosing
Date:
Subject: advice for user column named cmin