| From: | C Wegrzyn <lists(at)garbagedump(dot)com> |
|---|---|
| To: | Michael Meskes <meskes(at)postgresql(dot)org> |
| Cc: | Michael Fuhr <mike(at)fuhr(dot)org>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #1962: ECPG and VARCHAR |
| Date: | 2005-10-14 19:15:13 |
| Message-ID: | 435003C1.70802@garbagedump.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers pgsql-patches |
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
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim C. Nasby | 2005-10-14 19:33:12 | Re: BUG #1956: Plpgsql top-level DECLARE does not share scope |
| Previous Message | Tom Lane | 2005-10-14 18:18:32 | Re: [BUGS] Bug#333854: pg_group file update problems |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2005-10-14 20:34:43 | Re: A costing analysis tool |
| Previous Message | Tom Lane | 2005-10-14 18:37:37 | Re: A costing analysis tool |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2005-10-14 21:19:24 | Re: [BUGS] Bug#333854: pg_group file update problems |
| Previous Message | Tom Lane | 2005-10-14 18:18:32 | Re: [BUGS] Bug#333854: pg_group file update problems |