| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Michael Glaesemann <grzm(at)seespotcode(dot)net> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [PATCHES] possible ecpg vpath build error |
| Date: | 2006-09-04 04:06:02 |
| Message-ID: | 9809.1157342762@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Michael Glaesemann <grzm(at)seespotcode(dot)net> writes:
> There's a lot of duplicate code in ecpg.
No kidding :-(. The parser is bad enough but the datatype library is
an order of magnitude worse. I don't have a great solution at hand
though. The backend utils/adt/ code gets to rely on the backend's
error handling and memory management protocols, which I surely do
not propose to remove, but how could we keep common sources when
ecpglib has to work in a far less friendly environment?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeroen T. Vermeulen | 2006-09-04 04:12:13 | Re: Optimizing prepared statements |
| Previous Message | Michael Glaesemann | 2006-09-04 03:57:32 | Re: [PATCHES] possible ecpg vpath build error |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-09-04 04:12:39 | Re: [PATCHES] possible ecpg vpath build error |
| Previous Message | Bruce Momjian | 2006-09-04 03:57:38 | Re: [HACKERS] Interval aggregate regression failure |