Re: ecpg: arrays and nulls

From: Michael Meskes <meskes(at)postgresql(dot)org>
To: Kuba Ouhrabka <kuba(at)comgate(dot)cz>
Cc: pgsql-interfaces(at)postgresql(dot)org
Subject: Re: ecpg: arrays and nulls
Date: 2005-08-23 09:53:38
Message-ID: 20050823095338.GB8559@1
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-interfaces

On Tue, Aug 02, 2005 at 10:40:23AM +0200, Kuba Ouhrabka wrote:
> I'd like to ask how to handle null values when fetching arrays into
> ecpg. Always I get this error:
>
> Data read from backend is not an array in line ...

Found it. The check for array data was doen too early. Of course a
NULL does not look like an array, so the message was issued before the
data was tested on NULL values. I changed the order and it appears to be
fine now. Expect a commit as soon as I am online again.

> Can null values in columns of array type be handled in more convenient
> way than using coalesce/nullif and special reserved value?

Not sure what you mean with this? Do you want an integer array like
this {1,2,3,NULL,4,5}? I don't see how this could be possible as the
array itself is the value of the column. You can of course use a
relation instead of an array. In first normalform this should be easy to
do.

Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: meskes(at)jabber(dot)org
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!

In response to

Responses

Browse pgsql-interfaces by date

  From Date Subject
Next Message Zahid Khan 2005-08-24 06:27:08 BLOB in npgsql?
Previous Message Michael Meskes 2005-08-23 09:31:46 Re: ecpg and VARCHAR