From: Sergey S. Kosyakov <ks@itp.ac.ru>
To: Vadim B. Mikheev <vadim@sable.krasnoyarsk.su>
Cc: pgsql-questions@postgreSQL.org
Cc: pgsql-interfaces@postgreSQL.org
Subject: Re: [QUESTIONS] update NOT NULL via LIBPQ
Date: Wed, 25 Mar 1998 12:04:45 +0300 (MSK)
Message-ID: <XFMail.980325120742.ks@itp.ac.ru> (raw)
In-Reply-To: <3518C6C4.FBFF7AEE@sable.krasnoyarsk.su>
Yes. But I talk about LIBPQ. There should be some additional error code
like PGRES_QUERY_FAIL to distinguish from backend crash.
Sergey.
On 25-Mar-98 Vadim B. Mikheev wrote:
>Sergey S. Kosyakov wrote:
>>
>> Hi!
>>
>> Why PQexec(conn,query) returns FATAL_ERROR when query is update on
>> NOT NULL column with NULL value? The same error is produced when
>> backend core dumps, etc - that is, in the cases of TRUE fatal error.
>> I think that error status should not be equal for illegal query and
>> backend crashes.
>
>vac=> create table test (x int not null);
>CREATE
>vac=> insert into test values (1);
>INSERT 18473 1
>vac=> update test set x = null;
>ERROR: ExecReplace: Fail to add null value in not null attribute x
>
>Vadim
---
----------------------------------
Sergey Kosyakov
Laboratory of Distributed Computing
Department of High-Performance Computing and Applied Network Research
Landau Institute for Theoretical Physics
E-Mail: ks@itp.ac.ru
Date: 25-Mar-98
Time: 12:04:47
----------------------------------
---
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 using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: ks@itp.ac.ru, vadim@sable.krasnoyarsk.su, pgsql-questions@postgreSQL.org
Subject: Re: [QUESTIONS] update NOT NULL via LIBPQ
In-Reply-To: <XFMail.980325120742.ks@itp.ac.ru>
* 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