Re: [INTERFACES] my problems with ecpg and arrays - Mailing list pgsql-interfaces

From Coleman, Andrew
Subject Re: [INTERFACES] my problems with ecpg and arrays
Date
Msg-id 78166D547FD9D2119FA700805F9FA971C0E9A2@navont3.navo.navy.mil
Whole thread Raw
In response to [INTERFACES] my problems with ecpg and arrays  ("Coleman, Andrew" <colemana@navo.navy.mil>)
Responses Re: [INTERFACES] my problems with ecpg and arrays  (Michael Meskes <meskes@postgreSQL.org>)
List pgsql-interfaces
Thanks for looking into it. For the code I'm working on, it's no problem to
work around (messy, but
no problem).
>I'm afraid you find a real problem here. I just didn't think about
inserting
>arrays. If you give ecpg an array of int it inserts every single value as
>one int. That means:
>
>insert into foo(bar) values(:intarray)
>
>is equal to:
>
>for (i=0;i<maxarray;i++)
>    insert into foo(bar) values(:intarray[i])
>How shall ecpg see that this time it is meant to insert the whole array?
>
>Anyone with an idea?

I'm guessing you're mostly directing that at people who are atleast vaguely
familiar with the
way pg and ecpg works internally ;)

>
>Michael

Thanks again (both for looking into it and for ecpg itself),
andrew.



pgsql-interfaces by date:

Previous
From: "Tim Joyce"
Date:
Subject: Re: [INTERFACES] ResultSet.getDate
Next
From: joedbat@zaz.com.br
Date:
Subject: subscribe