From: | Rod Taylor <rbt(at)zort(dot)ca> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | tim(at)ametco(dot)co(dot)uk, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: Bug #759: 7.3beta1 DROP COLUMN DEPENDENCY PROBLEM |
Date: | 2002-09-06 13:28:06 |
Message-ID: | 1031318888.3555.2.camel@jester |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Fri, 2002-09-06 at 09:17, Tom Lane wrote:
> Rod Taylor <rbt(at)zort(dot)ca> writes:
> > Indeed. At the INNER JOIN it would appear that an alias is applied to
> > the columns of a given table.
> > ...
> > The real trick is to make INNER JOINS less greedy in their requirements
> > based on the columns that are actually used.
>
> What surprised me about this report was not that the JOIN syntax exposed
> a dependency on column c, but that the non-JOIN syntax didn't. There
> shouldn't be any semantic difference AFAIR, so it seems to me that at
> least one of these behaviors needs to be fixed.
>
> I am not sure that it's practical to remove the dependency as Tim is
> hoping for...
I wondered about that too, but by that time figured I was in way over my
head.
The big difference is that the INNER JOIN code needs to drop one of the
colb's coming up with a virtual relation cola, colb, colc; where the
other doesn't have such a renaming scheme.
Or, thats how it appears to function to the user. I've not dug into the
internals.
From | Date | Subject | |
---|---|---|---|
Next Message | Ronald Kuczek | 2002-09-06 13:41:50 | Unable to compile 7.3beta1 on cygwin |
Previous Message | Tom Lane | 2002-09-06 13:17:15 | Re: Bug #759: 7.3beta1 DROP COLUMN DEPENDENCY PROBLEM |