Re: More DROP COLUMN

From: Hannu Krosing <hannu(at)tm(dot)ee>
To: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: More DROP COLUMN
Date: 2002-07-15 10:17:11
Message-ID: 1026728231.29268.10.camel@taru.tm.ee
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)020715(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Curt Sampson 2002-07-15 10:35:59 Re: More DROP COLUMN
Previous Message Zeugswetter Andreas SB SD 2002-07-15 09:10:03 Re: More DROP COLUMN