it's the same with loadercli in MAXDB 7.5.00.5.
With the SAPDB/MYSQL policy at the moment there will be only a update at MAXDB. :-(
Regards
Albert
Schildberg, Steffen schrieb:
Hi Albert,
Albert Steckenborn [mailto:[EMAIL PROTECTED]
i 've had the same probs with my tables. For all INT/FIXED values if have to define a "if" clause.
The default for NULL VALUES is completely ignored for this datatypes.
The problem (bug) is found and fixed at the development system (no idea when the next version is released; I could offer a patch). And it is even worse than the scenario you described. In case of char values and an empty value as a NULL value representation the Loader would not insert NULLs but real empty values :-((. Important here is the fact that the NULL value representation must be an empty value to get this error. It should work for other than empty values.
Regards, Steffen
-- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
