 |
 |
Archives of the TeradataForum
Message Posted: Tue, 04 May 2004 @ 14:42:05 GMT
Subj: | | Re: Case sensitivity modifier in IN clause |
|
From: | | Dieter Noeth |
Michael Larkins wrote:
| There is no need to use the CS or NOT CS on both sides of the comparison operator. If one side is CS, both sides are the same. It is a
single comparison. So, putting the attribute of CASESPECIFIC on the column name is sufficient and this works fine in all releases. | |
This is only true in a Teradata mode session. If a session is run in ANSI mode, then each literal is casespecific. And if one of both
sides is casespecific then the comparison is casespecific...
Dieter
| |