Archives of the TeradataForum
Message Posted: Fri, 07 Nov 2003 @ 17:15:41 GMT
| Subj: | | Re: Queryman ANSI Mode |
| |
| From: | | Dieter Noeth |
Geoffrey Rommel wrote:
| | This applies EVEN IF LastName is defined as NOT CaseSpecific. [I don't know what the ANSI folks were smoking when they made that
decision... but that's the rules.] | |
Teradata's CaseSpecific is an extension to Standard SQL, according to ANSI the only way to get case insensitive results is using
UPPER/LOWER on both sides.
| | Probably the same thing they were smoking when they made "on commit delete rows" the default! | |
In Standard SQL that's ok, because you always have to manually COMMIT a transaction. Of course it's stupid for a Teradata session, but
NCR is implementing everything ANSI compliant including the stupid stuff :-(
- maximum number of digits for an Interval: 4 (Oracle has 9)
- date '2000-01-31' + interval '1' month: invalid date (at least you can use add_months instead)
Dieter
| 
