Hello,
we are using a MaxDB 7.6 instance (7.6.00 Build 012-123-102-632 on
Windows Server 2003 Std.Edt. SP1) and recognized corrupt TIMESTAMP data in
a column that is filled automatically by default via SQL function TIMESTAMP
(-> DDL: ...CREATE_DATE TIMESTAMP NOT NULL DEFAULT TIMESTAMP...; the rest
of the row is generated by an INSERT statement in a dbproc). The corrupted
data seems to have systematically a "wrong INTERNAL format":
<YYYMMDDHHMMSSMMMMMMY> instead of <YYYYMMDDHHMMSSMMMMMM>. Selecting this
column via SQL Studio shows blank fields, when using the zoom window one
gets "[MySQL MaxDB][SQLOD32 DLL] General error". (I suspect this resembles
the cause of the SYSERROR -9999 I reported on December 5th 2005.)
Data example (exported via loadercli):
("SCM_ID","CREATE_DATE")
"1500","20051202111441973000" (correct)
"1501","00512131835252830002" (corrupted)
"1502","00512131837119380002" (corrupted)
"1503","00512131842326860002" (corrupted)
"1504","00512131940546010002" (corrupted)
"1505","00512132033385470002" (corrupted)
"1506","00512132124416840002" (corrupted)
"1507","00512132216448830002" (corrupted)
"1508","00512132309005350002" (corrupted)
Unfortunately we did not get any error messages.
Is there someone who has an idea what going wrong? - Thanks in advcance!
kind regards
Frank
--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
