| From: | Michael Fuhr <mike(at)fuhr(dot)org> |
|---|---|
| To: | Marco Colombo <pgsql(at)esiway(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Martijn van Oosterhout <kleptog(at)svana(dot)org>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: plpython function problem workaround |
| Date: | 2005-03-18 15:16:57 |
| Message-ID: | 20050318151657.GA54630@winnie.fuhr.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, Mar 18, 2005 at 11:34:46AM +0100, Marco Colombo wrote:
> Just let me suggest not to mimic its behaviour, but to use the
> Real Thing if we manage to. That is, directly use the Universal Line
> Support code provided by python itself, so that we don't even have
> to think about being compatible.
Sounds good if the Python API provides the hooks for doing so. I
had started looking into that but didn't spent much time on it.
> I'm experimenting a bit, trying to write a PLy_procedure_compile()
> that does not require source munging. I'm aiming at removing the
> need for extra indentation.
Sounds good too, if that'll work. Looking forward to seeing what
you find out.
--
Michael Fuhr
http://www.fuhr.org/~mfuhr/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-03-18 15:29:29 | Re: pg_atributes index space question |
| Previous Message | Tom Lane | 2005-03-18 14:58:34 | Re: pg_dump large-file support > 16GB |