 |
 |
Archives of the TeradataForum
Message Posted: Wed, 11 Oct 2006 @ 13:21:45 GMT
Subj: | | Re: Index columns reversed in SHOW TABLE |
|
From: | | Joseph V D silva |
Victor Sokovin wrote:
| It would be interesting if somebody could comment on why exactly Teradata went for commutativity. I can't recall seeing any background
information on this. My guess is that although commutativity implied higher probability of hash collisions it was more economical to implement /
easier to program, and the higher collision rate was still low enough for anything practical. But this is just my guess. | |
Me thinks it's also due to high amount of joins that could be AMP local if hash(A,B) = hash (B,A)
Joseph Vinish D'silva
| |