| From: | Michael Meskes <meskes(at)postgresql(dot)org> |
|---|---|
| To: | Pavel PaJaSoft Janousek <janousek(at)fonet(dot)cz> |
| Cc: | PgSQL Interfaces <pgsql-interfaces(at)postgresql(dot)org> |
| Subject: | Re: [INTERFACES] Error in ECPG and #if... |
| Date: | 1999-04-21 11:52:04 |
| Message-ID: | 19990421135204.B343@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-interfaces |
On Tue, Apr 20, 1999 at 05:59:13PM +0200, Pavel PaJaSoft Janousek wrote:
> I use ECPG distributed with PostgreSQL 6.4.2. and I found next
> error..:-(
Not really.
> ECPG don't know C/C++ preprocessing directives such as #if, #ifdef
> etc...
That's correct. ECPG only parses stuff between EXEC SQL and ';'.
> 15. #if 0
> 16. exec sql select count (*) from
> 17. exec sql commit;
> 18. #endif
This is not C code.
> In this ECPG say: parse error on line 16.
Yes, because ECPG parses all embedded SQL code. It does not know about cpp
code.
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 | Per Rønne | 1999-04-21 13:12:55 | |
| Previous Message | Michael Meskes | 1999-04-21 11:49:24 | Re: [INTERFACES] ecpg cursors and scope |