Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
3 table join
Message
From
17/02/2011 09:39:49
Thomas Ganss (Online)
Main Trend
Frankfurt, Germany
 
General information
Forum:
Visual FoxPro
Category:
Databases,Tables, Views, Indexing and SQL syntax
Title:
Environment versions
Visual FoxPro:
VFP 8 SP1
Miscellaneous
Thread ID:
01500313
Message ID:
01500526
Views:
32
>>In a full join having the fastest way to calc each line may be important.
>>I'm pretty sure that
select nvl(T.PK, P.PK) as PK, nvl(T.FK, P.FK) AS FK, P.pNo, P.pDesc, T.tno, T.tDesc;
>>from Parts P full join Tools T on P.PK = T.PK and P.FK = T.FK into cursor csrToolsParts
>>
>>
>>is easier on resources and for my taste on the eyes as well ;-)
>
>I'm not exactly sure how does it work. It should work only if for each Main table PK we have sequence numbering without gaps, e.g.
>
>Main PK = 1
>FK = 1, 2, 3 in both tables.

Me neither - full join reasons are rare. At least half full joins I encountered were bugs.
But remapping iif(isnull(T.key), p.key, T.key) should not create problems.
Previous
Reply
Map
View

Click here to load this message in the networking platform