Re: ecpg weird behavior - Mailing list pgsql-interfaces

From Nicolas Bazin
Subject Re: ecpg weird behavior
Date
Msg-id 002401c1cfa1$b6032bf0$660d090a@software.ingenico.com.au
Whole thread Raw
In response to ecpg weird behavior  ("Nicolas Bazin" <nbazin@ingenico.com.au>)
Responses Re: ecpg weird behavior
Re: ecpg weird behavior
List pgsql-interfaces
----- Original Message -----
From: "Michael Meskes" <meskes@postgresql.org>
To: "Thomas Lockhart" <thomas@fourpalms.org>
Cc: "Michael Meskes" <meskes@postgresql.org>; "Nicolas Bazin"
<nbazin@ingenico.com.au>; <pgsql-interfaces@postgresql.org>
Sent: Wednesday, March 20, 2002 6:16 AM
Subject: Re: [INTERFACES] ecpg weird behavior


> On Fri, Mar 15, 2002 at 09:11:34AM -0800, Thomas Lockhart wrote:
> > btw, I was working for the first time with ecpg and was very impressed.
>
> Thanks.
>
> > A company porting from Oracle ran into very few issues. Their existing
> > code *did* have an Oracle extension to use a cursor to select multiple
> > rows into variables declared as arrays. Have you run into this syntax or
> > thought about what it would take to implement it?
>
> Do you mean like this:
>
> exec sql begin declare section;
> int amount[6];
> char name[6][8];
> exec sql end declare section;
> ...
> exec sql select * into :name, :amount from "Test";
no what would work is
exec sql select * into :var1[i].name :var1[i].amount from "Test";

>
> This example btw is taken from test1.pgc under ecpg/test and thus is
> fully supported.
>
> Michael
> --
> Michael Meskes
> Michael@Fam-Meskes.De
> Go SF 49ers! Go Rhein Fire!
> Use Debian GNU/Linux! Use PostgreSQL!
>




pgsql-interfaces by date:

Previous
From: Jeremy Buchmann
Date:
Subject: Re: Problem with pgaccess
Next
From: "Nicolas Bazin"
Date:
Subject: Re: ecpg weird behavior