Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: BUG #3181: ecpg generating wrong code
- From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- To: "Steve Gieseking" <steve(dot)gieseking(at)camotion(dot)com>
- Cc: pgsql-bugs(at)postgresql(dot)org
- Subject: Re: BUG #3181: ecpg generating wrong code
- Date: Mon, 26 Mar 2007 23:27:15 -0400
"Steve Gieseking" <steve(dot)gieseking(at)camotion(dot)com> writes:
> I am maintaining code that uses ecpg. The following query was working with
> the previous version of ecpg:
> ...
> The problem is the translation to ensable. This appears to be caused by the
> file 'preproc.y' at the line:
> | ENABLE_P { $$ = make_str("ensable"); }
Good catch, but AFAICS this was broken in 8.1 as well. What "previous
version" are you comparing to?
regards, tom lane
- References:
- BUG #3181: ecpg generating wrong code
- From: Steve Gieseking
- BUG #3181: ecpg generating wrong code
- Prev by Date: Re: BUG #3048: pg_dump dumps intarray metadata incorrectly
- Next by Date: Re: "Relation not found" error but table exits.
- Previous by thread: BUG #3181: ecpg generating wrong code
- Next by thread: BUG #3182: Cannot make libpq with BCC 5.5
- Indexes: