Re: [HACKERS] Well, then you keep your darn columns

From: Ed Loehr <eloehr(at)austin(dot)rr(dot)com>
To: Don Baccus <dhogaza(at)pacifier(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [HACKERS] Well, then you keep your darn columns
Date: 2000-01-24 20:26:40
Message-ID: 388CB580.6B336648@austin.rr.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Don Baccus wrote:
>
> >How would you handle multi-column indices that included the column
> >being dropped? E.g.,
> >
> > create unique index foobar on mytable(foo,bar);
> >
> >where the 'bar' column is then dropped...
>
> ... Oracle drops all indices which reference the column.

Seems like a new 'gotcha'... either way, informative warnings/notices
would be nice.

Along these same lines, how would pre-existing functions that
referenced the just-dropped column be handled? I'm thinking of
PL/pgSQL...

Cheers,
Ed Loehr

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Don Baccus 2000-01-24 20:29:48 Re: [HACKERS] Well, then you keep your darn columns
Previous Message The Hermit Hacker 2000-01-24 20:24:26 Re: [HACKERS] Well, then you keep your darn columns