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

Re: ECPG include problem

From: Christoph Haller <ch(at)rodos(dot)fzk(dot)de>
To: pgsql-interfaces(at)postgresql(dot)org
Cc: meskes(at)postgresql(dot)org
Subject: Re: ECPG include problem
Date: 2003-02-24 10:26:39
Message-ID: 3E59F35F.6065B5A7@rodos.fzk.de (view raw or flat)
Thread:
Lists: pgsql-interfaces
>
> Ingres preprocessor does parse C and CPP code as well, ecpg does not.
It
> only parses stuff after an exec sql keyword is found. The only way for

> you get this going is to use "exec sql define" instead of "#define" as

> the former is parsed an honored by ecpg. Of course you could as well
try
> running cpp over the files before but that won't always work.
>
Looks like a lack of documentation. Maybe I am wrong, but I could not
find anything about the existence of "exec sql define".

Regards, Christoph



Responses

pgsql-interfaces by date

Next:From: Christoph HallerDate: 2003-02-24 14:25:44
Subject: Re: Using LISTEN/NOTIFY with ecpg
Previous:From: Matthew VanecekDate: 2003-02-22 17:23:55
Subject: Using LISTEN/NOTIFY with ecpg

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