I wrote:
> Hmm. Trying this here, I get
> ...
Oh, scratch that, I'd failed to duplicate the test case. (I had an
empty string, not NULL, as the value of the tstchar25 column.)
I concur with Laurenz's diagnosis that you need to use an indicator
variable if you want to retrieve a NULL.
Matthias Apitz writes:
> El día Mittwoch, Juni 17, 2020 a las 01:39:53 -0400, Tom Lane escribió:
>> Could you provide a self-contained test case for this? It's hard to
>> guess at what the problem might be.
> attached is a simple ESQL/C code;
> ...
> [6485] [18.06.2020 08:26:38:436]: ecpg_execut
On Wed, 2020-06-17 at 19:02 +0200, Matthias Apitz wrote:
> We encountered that if our ESQL/C written servers see on SELECT or FETCH
> in a row a NULL value, it will raise correctly the error -213 as written
> and explained in
> https://www.postgresql.org/docs/11/ecpg-variables.html#ECPG-INDICATORS
El día Mittwoch, Juni 17, 2020 a las 01:39:53 -0400, Tom Lane escribió:
> Matthias Apitz writes:
> > We encountered that if our ESQL/C written servers see on SELECT or FETCH
> > in a row a NULL value, it will raise correctly the error -213 as written
> > and explained in
> > https://www.postgres
Matthias Apitz writes:
> We encountered that if our ESQL/C written servers see on SELECT or FETCH
> in a row a NULL value, it will raise correctly the error -213 as written
> and explained in
> https://www.postgresql.org/docs/11/ecpg-variables.html#ECPG-INDICATORS
> We catch this error -213 and d
Hello,
We encountered that if our ESQL/C written servers see on SELECT or FETCH
in a row a NULL value, it will raise correctly the error -213 as written
and explained in
https://www.postgresql.org/docs/11/ecpg-variables.html#ECPG-INDICATORS
We catch this error -213 and deal with in.
What we di
