Re: no current record for fetch operation mining explicit left joins and implicit inner joins

Article View: borland.public.interbase.sql

Article #117

Back to borland.public.interbase.sql Previous Next

#117

From: Bill Todd [TeamB]
Date: Fri, 06 Jun 2008 17:27

20 lines
2112 bytes

Massimiliano Trezzi wrote:

>    It's a bug and it's clear that it's not designed to be so.

"As designed" means as designed by the software engineers responsible
for the product. It may not work the way you want it to and it may not
work the way the SQL standard says it should but, as Quinn stated, it
does work the way the R&D team intended. Therefore, this behavior is
not a bug. If you disagree with this please look in any dictionary of
software engineering terms for the definition of a bug.

I certainly agree with you that IB should be changed so that SQL that
does not execute correctly either does not execute at all or that it
does execute correctly. I do disagree with you in that I think the best
fix for IB is to generate an error message and not execute the SQL.
There are too many move valuable things that R&D can spend time on to
invest their time in making IB support mixed mode joins.

-- 
Bill Todd (TeamB)

Technical Details

Message-ID: <48497398@newsgroups.borland.com>

Path:

arc1-ca.pugleaf.net!g2news1.google.com!news2.google.com!news.glorb.com!feeder.erje.net!newsfeed01.sul.t-online.de!t-online.de!newsgroups.borland.com!not-for-mail

References:

<483d879c$1@newsgroups.borland.com> <483e198f$1@newsgroups.borland.com> <483e8221$1@newsgroups.borland.com> <483eb8db$1@newsgroups.borland.com> <4848ffb4$1@newsgroups.borland.com> <48494656$1@newsgroups.borland.com> <484960e0@newsgroups.borland.com>

Show Full Headers

Complete Article Headers

X-Google-Thread: 114a0e,c962a98f7a2cfe5f
X-Google-Attributes: gid114a0e,domainid0,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
From: "Bill Todd [TeamB]" <no@no.com>
Subject: Re: no current record for fetch operation mining explicit left joins and implicit inner joins
Newsgroups: borland.public.interbase.sql
References: <483d879c$1@newsgroups.borland.com> <483e198f$1@newsgroups.borland.com> <483e8221$1@newsgroups.borland.com> <483eb8db$1@newsgroups.borland.com> <4848ffb4$1@newsgroups.borland.com> <48494656$1@newsgroups.borland.com> <484960e0@newsgroups.borland.com>
Organization: The Database Group, Inc.
User-Agent: XanaNews/1.18.1.9
X-Face: ":yn4zt^A_dn>6~{YJmu^B\'4w)e:apPM\VC=Dvf&*tASxX9|BYczkFd$xr.$vNSZ[3Uobr p]c4\+\l){!WQI.$]veP({HLd;CDYH?iN
NNTP-Posting-Host: 63.147.41.232
Message-ID: <48497398@newsgroups.borland.com>
Date: 6 Jun 2008 10:27:52 -0700
X-Trace: newsgroups.borland.com 1212773272 63.147.41.232 (6 Jun 2008 10:27:52 -0700)
Lines: 20
X-Authenticated-User: btodd
Path: arc1-ca.pugleaf.net!g2news1.google.com!news2.google.com!news.glorb.com!feeder.erje.net!newsfeed01.sul.t-online.de!t-online.de!newsgroups.borland.com!not-for-mail

Reply to Parent Message