From: Emils Klotins <emils@mail.usis.bkc.lv>
To: pgsql-sql@postgresql.org
Subject: 6.5.3 - backend closes if wrong parameters to NULLIF, CASE
Date: Fri, 26 Nov 1999 17:48:02 EET
Message-ID: <15394638353950@bkc.lv> (raw)
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.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-sql@postgresql.org
Cc: emils@mail.usis.bkc.lv
Subject: Re: 6.5.3 - backend closes if wrong parameters to NULLIF, CASE
In-Reply-To: <15394638353950@bkc.lv>
References: <15394638353950@bkc.lv>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox