 |
 |
Archives of the TeradataForum
Message Posted: Sat, 31 Mar 2007 @ 20:07:31 GMT
Subj: | | Re: Order of inner joins alter plan |
|
From: | | Anomy Anom |
<-- Anonymously Posted: Saturday, March 31, 2007 13:24 -->
| At one time there was a discussion thread on the different plans from the original syntax versus the join syntax. However, I seem to
remember Todd Walter posting a message regarding the fact that developers realized there was a difference and were in the process or planning to
fix it. Since that was quite some time ago, I am sort of hopeful that it has already been corrected. | |
I'll agree, my understanding is that changing the order of joins or where predicates should not change the execution plan. I also recall
hearing that if anyone found this kind of behavior, Teradata wanted to know about it. I'd suggest submitting the queries as a priority 3 incident
- along with the appropriate supporting info (TSET).
| |