From: | Michael Meskes <meskes(at)postgresql(dot)org> |
---|---|
To: | Nicolas Bazin <nbazin(at)ingenico(dot)com(dot)au> |
Cc: | Thomas Lockhart <thomas(at)fourpalms(dot)org>, Michael Meskes <meskes(at)postgresql(dot)org>, pgsql-interfaces(at)postgresql(dot)org |
Subject: | Re: ecpg weird behavior |
Date: | 2002-03-19 19:18:48 |
Message-ID: | 20020319191848.GC3893@feivel.fam-meskes.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-interfaces |
On Mon, Mar 18, 2002 at 10:41:41AM +1100, Nicolas Bazin wrote:
> Yes I also have this issue. From what I read in the ecpg doc, indexed
> variables are not supported by ecpg and trying to compile the code definitle
Yes, there's an open TODO for that.
> proved it is not supported. The way I work arround it is to declare a local
> variable of the same type, copy the array element into this variable,
> perform the FECTH or SELECT and then copy the variable back into the array
> element. I guess the preprocessor could also generate the code.
It should be even easier. I think the parser could handle that directly.
> Another issue I had that ecpg does not support prepared statements. But I
> didn't have that many prepared statements so I just rewrote the code.
ECPG just simulates a prepare statement, but that should not qualify as
"not support". So what didn't work?
Michael
--
Michael Meskes
Michael(at)Fam-Meskes(dot)De
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use PostgreSQL!
From | Date | Subject | |
---|---|---|---|
Next Message | Jeremy Buchmann | 2002-03-19 23:04:17 | Re: Problem with pgaccess |
Previous Message | Michael Meskes | 2002-03-19 19:16:53 | Re: ecpg weird behavior |