Re: BUG #1962: ECPG and VARCHAR - Mailing list pgsql-bugs

From C Wegrzyn
Subject Re: BUG #1962: ECPG and VARCHAR
Date
Msg-id 435003C1.70802@garbagedump.com
Whole thread Raw
In response to Re: BUG #1962: ECPG and VARCHAR  (Michael Meskes <meskes@postgresql.org>)
Responses Re: BUG #1962: ECPG and VARCHAR
List pgsql-bugs
The customer I am writing this for will only accept it based on released
code. That means I run either 8.0.3 or 8.0.4.

Chuck

Michael Meskes wrote:

>On Thu, Oct 13, 2005 at 11:18:13AM -0500, C Wegrzyn wrote:
>
>
>> Yes I found out the same thing. Unfortunately it isn't quite that
>>simple for me. It isn't a very good idea to hard-code fixed sizes in
>>executables. I have a file with all sorts of #defines in it. If the bug
>>doesn't get fixed it means that I will need to run CPP over the code
>>before I run ecpg, which is just ugly.
>>
>>
>
>Can't you just compile a new version of ecpg with the patch Bruce
>committed? Depending on the system you're using I could even send you a
>binary.
>
>Michael
>
>

pgsql-bugs by date:

Previous
From: "Karl O. Pinc"
Date:
Subject: Re: BUG #1956: Plpgsql top-level DECLARE does not share
Next
From: "Jorge Mario Valencia"
Date:
Subject: BUG #1968: bad end of file