From: | Michael Meskes <meskes(at)postgresql(dot)org> |
---|---|
To: | Pavel PaJaSoft Janousek <janousek(at)fonet(dot)cz> |
Cc: | Dave Broudy <shaggy(at)broudy(dot)net>, PgSQL Interfaces <pgsql-interfaces(at)postgresql(dot)org> |
Subject: | Re: [INTERFACES] ecpg cursors and scope |
Date: | 1999-04-22 15:50:17 |
Message-ID: | 19990422175017.A926@gmx.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-interfaces |
On Wed, Apr 21, 1999 at 12:36:59PM +0200, Pavel PaJaSoft Janousek wrote:
> I think, that principly is correct contructions like this:
No, to do this you need the PREPARE statement.
> ...
>
> One time I wrote this exec<space><space>sql - and ECPG say parse error
> too, but I forgot, that bad was only this two spaces between 'exec' and
> 'sql'....
Hmm, this is not good.
> Next, some 'interesting' situations I got when I use exec sql
> whenever... - scope for this is not as the program running, but as the
> source is parsing... - this is ...'-)
That's what the standard says. The whenever statement is a preprocessor
statement.
Michael
--
Michael Meskes | Go SF 49ers!
Th.-Heuss-Str. 61, D-41812 Erkelenz | Go Rhein Fire!
Tel.: (+49) 2431/72651 | Use Debian GNU/Linux!
Email: Michael(dot)Meskes(at)gmx(dot)net | Use PostgreSQL!
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Meskes | 1999-04-22 15:53:40 | Re: [INTERFACES] Comment in ECPG - again |
Previous Message | Per Rønne | 1999-04-22 13:53:16 | RE: [INTERFACES] Possible error in libpg++ interface, date[time] fields. |