| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Matthias Apitz <guru(at)unixarea(dot)de> |
| Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: ESQL/C no indicator variables ./. error -213 |
| Date: | 2020-06-18 15:21:02 |
| Message-ID: | 1550181.1592493662@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2020-06-18 16:08:23 | Re: create batch script to import into postgres tables |
| Previous Message | Pepe TD Vo | 2020-06-18 15:20:07 | Re: create batch script to import into postgres tables |