From: | "Sergey S(dot) Kosyakov" <ks(at)itp(dot)ac(dot)ru> |
---|---|
To: | "Vadim B(dot) Mikheev" <vadim(at)sable(dot)krasnoyarsk(dot)su> |
Cc: | pgsql-questions(at)postgreSQL(dot)org, pgsql-interfaces(at)postgreSQL(dot)org |
Subject: | Re: [QUESTIONS] update NOT NULL via LIBPQ |
Date: | 1998-03-25 09:04:45 |
Message-ID: | XFMail.980325120742.ks@itp.ac.ru |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-interfaces |
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(at)itp(dot)ac(dot)ru
Date: 25-Mar-98
Time: 12:04:47
----------------------------------
---
From | Date | Subject | |
---|---|---|---|
Next Message | Constantin Teodorescu | 1998-03-25 10:12:38 | Re: [QUESTIONS] Char types with ODBC and Access 97 |
Previous Message | Pierre Habraken | 1998-03-25 08:57:26 | JBuilder QueryDataSet: Can't browse tables in Query Editor |