Skip site navigation (1) Skip section navigation (2)

Re: ecpg weird behavior

From: Michael Meskes <meskes(at)postgresql(dot)org>
To: Nicolas Bazin <nbazin(at)ingenico(dot)com(dot)au>
Cc: pgsql-interfaces(at)postgresql(dot)org
Subject: Re: ecpg weird behavior
Date: 2002-03-15 08:21:24
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-interfaces
On Thu, Mar 14, 2002 at 05:16:41PM +1100, Nicolas Bazin wrote:
> It will know the variables when the cursor is declared. Here is the syntax
> that we currently use with INFORMIX and it also corresponds to the syntax in
> the PostgreSQL documentation:

Where did you find this in the PostgreSQL docs?

It certainly is not implemented.

> FT_devises.dvs_devise,pays.pys_coddevalp,pays.pys_nbrdecimal
>     INTO :pays.pys_coddevnum, :pays.pys_coddevalp, :pays.pys_nbrdecimal
>     FROM pays, FT_devises WHERE FT_devises.dvs_code = :stpe.tpe_profdevise
>     AND FT_devises.dvs_devise = pays.pys_coddevnum;
> EXEC SQL FETCH curs_currency;

Anyone out there with more knowledge about standards? I thought this was
not standard at all.

> > Yes, I am. Please send it to me directly at meskes(at)postgresql(dot)org(dot)
> This patch breaks backward compatibility. The idea was to change the output
> of the preproc when it parses EXEC SQL type mytpe is ... from comment to the
> proper typedef definition. Then the typedef doesn't have to be added
> manually. If you still want it, I can send it.

I still want it. After all I can change the behaviour with a command
line option.

Michael Meskes
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use PostgreSQL!

In response to


pgsql-interfaces by date

Next:From: Marco KienzleDate: 2002-03-15 09:37:28
Subject: perl dbi postgresql uppercase problem
Previous:From: jtvDate: 2002-03-15 02:59:44
Subject: Re: Reset?

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group