From: | Michael Fuhr <mike(at)fuhr(dot)org> |
---|---|
To: | Michael Meskes <meskes(at)postgresql(dot)org>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Connection string |
Date: | 2006-08-15 11:59:23 |
Message-ID: | 20060815115923.GA99861@winnie.fuhr.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Sun, Aug 13, 2006 at 10:30:24AM +0200, Michael Meskes wrote:
> On Fri, Aug 11, 2006 at 04:40:36PM -0600, Michael Fuhr wrote:
> > Will you take care of it or should I submit a patch? I've noticed
>
> I you have the time to write the patch I woul dappreciate it.
I'll submit a patch. However, in the case of string literals not
working, is that a documentation bug or a code bug? Are they
supposed to work?
> > a few other discrepancies between the documentation and actual
> > behavior, like examples with "VARCHAR val;" that the preprocessor
> > rejects with "ERROR: pointer to varchar are not implemented."
>
> Do you have an example? This surely looks like a bug.
See several code examples in the last half of the "Using Host
Variables" documentation:
http://www.postgresql.org/docs/8.1/interactive/ecpg-variables.html
Here's a complete example with code pasted from the documentation:
% cat foo.pgc
int main(void)
{
EXEC SQL BEGIN DECLARE SECTION;
int v1;
VARCHAR v2;
EXEC SQL END DECLARE SECTION;
return 0;
}
% ecpg foo.pgc
foo.pgc:5: ERROR: pointer to varchar are not implemented
Is that a documentation bug or a code bug?
--
Michael Fuhr
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Sabino Mullane | 2006-08-15 12:24:06 | Re: Excluding a table from pg_dump |
Previous Message | Pavel Velikhov | 2006-08-15 11:38:08 | Using SETOF functions in SQL |