Re: ecpg weird behavior - Mailing list pgsql-interfaces

From Michael Meskes
Subject Re: ecpg weird behavior
Date
Msg-id 20020313141623.GE15148@credativ.de
Whole thread Raw
In response to ecpg weird behavior  ("Nicolas Bazin" <nbazin@ingenico.com.au>)
List pgsql-interfaces
On Thu, Mar 07, 2002 at 10:14:41AM +1100, Nicolas Bazin wrote:
> I'm porting an application from INFORMIX to Postgresql and have found weird behaviour of ecpg:
> - when using cursors, the fetch statement needs "into ..." which does not comply with the SQL syntax,

I'm not sure what you are talking about. FETCH with INTO does not comply
to which standard? SQL3 for instance says:

<fetch statement> ::=   FETCH [ [ <fetch orientation> ] FROM ]     <cursor name> INTO <fetch target list>

If I omit the INTO how shall it know the variables?

> - a type definition needs to be written twice: the C  version and the SQL version. It is easy to modify the preproc
toonly have the SQL definition (I have done it and can submit a patch if anyone is interested),
 

Yes, I am. Please send it to me directly at meskes@postgresql.org.

> Also I have found a bug in the way the preproc  handles preproc conditions "EXEC SQL IFDEF ...". I have submitted the
patchto fix it to hackers but it looks like it's been ignored.
 

It seems you mail got delayed as it just arrived in my mailbox. But I
take it this is the patch you already send me a few days ago (after all
this mail I'm replying to was written March 7th). So it should be in CVS
already.

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: rolf.ostvik@axxessit.no
Date:
Subject: Re: [GENERAL] PL/pgSQL Syntax Problem
Next
From: paul simdars
Date:
Subject: starting pgaccess