Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
David Williams — — source: Informix-list mailing list archive (1991-1998)
In article <5o3og1$fmb@romeo.logica.co.uk>, Akis Xenophontos
<akisx@logica.com> writes
>E-maill Address: akisx@logica.com
>Name: Akis Xenophontos
>Company: Logica UK Ltd
>Postal Address: London NW1
>Tel No: 0171 446 1324
>
>Date: 16/06/97
>
>A colleague has encountered the following problem in a live system:
>
>The bit of sql was of the form...
>
>UPDATE table
>SET col_1 = CURRENT YEAR TO MINUTE
>where col_2 = $col_2_id
>
>The $col_2_id was almost certainly ok otherwise we would have bombed out
>before this point.
>
>The informix errror code was -519 which indicates "Cannot update column to
>illegal value - One of the values in this update statement is based on an
>expression that is in
>error.Check each expression in the SET clause for validity, looking in
>particular at uses of built-in functions such as length and DATE."
>
>Does anyone know of a problem with using CURRENT YEAR TO MINUTE in a direct
>database update as we are doing here ?
>
>The system is operating using Informix OnLine V5.05
>
>
>Thanks in advance - Akis
>
What type is co1l is it a datetime year to minute?
--
David Williams
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.