Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2]) by hub.org (8.9.3/8.9.3) with ESMTP id NAA41534 for ; Fri, 26 Nov 1999 13:06:33 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.sss.pgh.pa.us (8.9.1/8.9.1) with ESMTP id NAA16142; Fri, 26 Nov 1999 13:06:00 -0500 (EST) To: "Emils Klotins" cc: pgsql-sql@postgreSQL.org Subject: Re: [SQL] 6.5.3 - backend closes if wrong parameters to NULLIF, CASE In-reply-to: Your message of Fri, 26 Nov 1999 17:48:02 EET <15394638353950@bkc.lv> Date: Fri, 26 Nov 1999 13:06:00 -0500 Message-ID: <16140.943639560@sss.pgh.pa.us> From: Tom Lane "Emils Klotins" writes: > 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. I get "Bad date external representation ''" from either 6.5.3 or current sources. Are you sure you're running 6.5.3, and not some older version? I fixed a lot of bugs involving CASE around 6.5 ... If it's not that, then there must be some other aspect of your example that's critical but you haven't shown us. Please file a formal bug report giving a complete SQL script that reproduces the bug. regards, tom lane