Subject | Re: Bug in firebird 1.5?? left joining |
---|---|
Author | johnsparrowuk |
Post date | 2004-03-18T14:34:30Z |
Hia Svein,
Thats for the clarification. I can see that:
years...!
I think I read it was efficient once... but might not have been a
reference to Interbase or Firebird..
John
--- In firebird-support@yahoogroups.com, "Svein Erling"
<svein.erling.tysvaer@k...> wrote:
Thats for the clarification. I can see that:
> select a.* from a whereIs clearer than the outer join, it's just something I've done for
> not exists(select * from b where a.id = b.id)
years...!
I think I read it was efficient once... but might not have been a
reference to Interbase or Firebird..
John
--- In firebird-support@yahoogroups.com, "Svein Erling"
<svein.erling.tysvaer@k...> wrote:
> --- In firebird-support@yahoogroups.com, "johnsparrowuk" wrote:and
> > Hi Svein,
> >
> > I didn't know about the restriction on the WHERE clause... I use
> >this structure a lot. Are you sure it's not ok to say:
> >
> > select a.* from a left join b on a.id = b.id where b.id is null
>
> No, I'm not saying I'm sure about that, just that it confuses me
> that I am curious about its use.FULL
>
> Maybe it is the equivalent of what I normally write as
>
> select a.* from a where
> not exists(select * from b where a.id = b.id)
>
> > ??? If it's not valid SQL, shouldn't Firebird refuse to accept it?
> > Also, if it's not valid to reference the 'outer' side of an outer
> > join, does that mean you can't have a WHERE clause at all in a
> > OUTER?!?!?!its
>
> The database I normally work with has one million rows or more in
> main tables, and I never use FULL OUTER JOIN on them ;o} You may beI
> right in that OUTER JOINed tables can be used in the where clause,
> might just have misread some advice on this list a while ago(though
> I'll continue to put my limiting criteria for the left joinedtables
> in my JOIN clause until I experience a case where it causesproblems).
>
> Set