Re: SQL OUTER JOIN giving unpredictable results

Article View: borland.public.vdbase.data.sql

Article #45

Back to borland.public.vdbase.data.sql Previous Next

#45

From: Mark Berry
Date: Tue, 23 Feb 1999 00:00

18 lines
1286 bytes

I think I figured out how to get the join to work:  

- Put the table containing orphaned records on the left side of a LEFT
OUTER JOIN.

- Explicitly specify field names, i.e. don't use "SELECT *".

- Issue last() and first() before checking endOfSet.

I guessed at the last part after noticing that the SQL grid didn't
correctly display rows until you scrolled down, then back up.  (Does
news of such anomolies ever get back to Inprise?  Or this VDB still
being developed/debugged?)

Unfortunately, I'm unable to delete the rows based on this rowset, but
it may be the best way to display rows before deletion.

Mark Berry

Technical Details

Message-ID: <36D34562.C4BC0224@nospam.mcbsys.com>

Path: arc1-ca.pugleaf.net!unknown!not-for-mail

References: <36CE28AB.704C343B@nospam.mcbsys.com> <36d799c1.4949355@forums.inprise.com> <36D1C1A3.FD15537E@nospam.mcbsys.com>

Show Full Headers

Complete Article Headers

X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: ff5a1,3dc8d9196f7bc07d
X-Google-Attributes: gidff5a1,public
From: Mark Berry <markb@nospam.mcbsys.com>
Subject: Re: SQL OUTER JOIN giving unpredictable results
Date: 1999/02/23
Message-ID: <36D34562.C4BC0224@nospam.mcbsys.com>
X-Deja-AN: 447693304
Content-Transfer-Encoding: 7bit
References: <36CE28AB.704C343B@nospam.mcbsys.com> <36d799c1.4949355@forums.inprise.com> <36D1C1A3.FD15537E@nospam.mcbsys.com>
Content-Type: text/plain; charset=us-ascii
Organization: MCB Systems
Mime-Version: 1.0
Reply-To: markb@nospam.mcbsys.com
Newsgroups: borland.public.vdbase.data.sql

Reply to Parent Message