| From: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | "Hannu Krosing" <hannu(at)tm(dot)ee> |
| 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 07:20:08 |
| Message-ID: | GNELIHDDFBOCMGBFGEFOIECFCDAA.chriskl@familyhealth.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> > 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!
Chris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Luis Alberto Amigo Navarro | 2002-07-15 07:45:36 | Re: [HACKERS] please help on query |
| Previous Message | Christopher Kings-Lynne | 2002-07-15 04:06:47 | Re: More DROP COLUMN |