 |
 |
Archives of the TeradataForum
Message Posted: Wed, 26 Sep 2001 @ 19:19:56 GMT
| Subj: | | Time formats |
| |
| From: | | Frank Martinez |
Hola a la lista de Teradata,
Well, this is a weird one I got from one of our developers. See the following not: No, we're not doing time stamps, we're just coding
the time in a CHAR(8) field (it's kind of a "maybe we'll use this someday" field, you know source widely?), but we are getting two different
results with different multiload scripts that both just refer to "TIME". Very strange, it's like the default format is changing in
different scripts with the EXACT same code. We solved it by just hard-coding the format, so it's not a solution I'm looking for, just for
someone to tell me what it is I've missed! Besides, NOBODY said anything about my question about SAMPLE and how to get a "truly" random
sample, so I got to bug you all!
iv
Frank C. Martinez IV
,LastUpdateDate DATE
,LastUpdateTime CHAR(8)
I have reloaded the tables using the system date and time in the multiload insert. The time format is not the same for the tables and I
can't see what I did different for the tables. See examples below. I prefer the format with colons, rather than a decimal. Any ideas?
This is not a high priority issue. As long as the time format is consistent within a table I can use either format. As an interesting note,
I'm using the same sort of insert in the MultiLoadStats table and the time always goes in with colons.
select drugcode, lastupdatedate, lastupdatetime
from hcftest.drugmaster
00536346735 2001-09-19 1.74750
08026840212 2001-09-19 1.74755
52544072901 2001-09-19 1.74807
38779005725 2001-09-19 1.74802
79854000140 2001-09-19 1.74819
select diagnosiscode, lastupdatedate, lastupdatetime
from hcftest.diagnosisicd9group
4749 2001-09-19 17:15:44
1223 2001-09-19 17:15:43
67304 2001-09-19 17:15:44
5339 2001-09-19 17:15:44
V074 2001-09-19 17:15:43
| |
