On Wed, Oct 9, 2013 at 5:50 PM, Gene Wirchenko <[email protected]> wrote:
> > I will stick with SQL not being very well-designed. For example, > select joincolumn, othercolumn1, othercolumn2; > from tableone join tabletwo; > on tableone.joincolumn=tabletwo.**joincolumn; > order by joincolumn > is incorrect, because joincolumn's table has to be specified! But it is > the same value either way! > ------------- > Actually you could gain performance because of an index used in table1 vs table2 thus you tell it which one to use. So they are not the same to the engine as they appear to you. >> Did you just do a distinct on what was there without a join to get your >> proper starting point? Then compare that rowcount against your lookup >> table for the descriptions? >> > > No. You saw my query. > ------------ > Just trying to give you a heads up on proof of data -- Stephen Russell Sr. Analyst Ring Container Technology Oakland TN 901.246-0159 cell --- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html --- _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/cajidmylch0os7-1v1pffu260l7pylf1fd0mkyfeqfeomqyu...@mail.gmail.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
