Received: from beta.bkc.lv (beta.bkc.lv [195.244.128.53]) by hub.org (8.9.3/8.9.3) with SMTP id KAA20790 for ; Fri, 26 Nov 1999 10:39:50 -0500 (EST) (envelope-from emils@mail.usis.bkc.lv) Received: from mail.usis.bkc.lv (mail.usis.bkc.lv [195.244.132.2]) by beta.bkc.lv (NTMail 3.02.13) with ESMTP id ha958341 for ; Fri, 26 Nov 1999 17:39:46 +0200 Received: from USIS-RIGA/SpoolDir by mail.usis.bkc.lv (Mercury 1.44); 26 Nov 99 17:48:15 EET Received: from SpoolDir by USIS-RIGA (Mercury 1.44); 26 Nov 99 17:48:02 EET From: "Emils Klotins" Organization: USIS Riga To: pgsql-sql@postgresql.org Date: Fri, 26 Nov 1999 17:48:02 EET MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: 6.5.3 - backend closes if wrong parameters to NULLIF, CASE Priority: normal X-mailer: Pegasus Mail for Win32 (v3.12b) Message-Id: <15394638353950@bkc.lv> Continuing to try to work with the things. I have a table "authors" with approx following fields: ( name text, id int4, birthdate date, ... , address_id int4 ) - when using a wrong CASE or NULLIF in INSERT/UPDATE statement on birthdate, it seems that it corrupts the address_id field. Ie. If I do a thing like UPDATE authors set birthdate=NULLIF(date '12-12-1999', date '') ... the backend will die and whenever afterwards I try to SELECT the address_id field from the updated row, it would die again. If I do a SELECT NULLIF(date '12-12-1999', date '') it will correctly complain that '' is a wrong date value. Seems also that when I try to UPDATE/INSERT using a CASE stmt it would die too, again corrupting the address_id field.