| From: | David <dbree(at)duo-county(dot)com> |
|---|---|
| To: | Michael Fuhr <mike(at)fuhr(dot)org> |
| Cc: | Ragnar Hafstað <gnari(at)simnet(dot)is>, David <dbree(at)duo-county(dot)com>, Sim Zacks <sim(at)compulab(dot)co(dot)il>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: plpython function problem workaround |
| Date: | 2005-03-16 13:17:26 |
| Message-ID: | 20050316131726.GB11121@localhost.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Mar 15, 2005 at 02:50:06PM -0700, Michael Fuhr wrote:
> On Tue, Mar 15, 2005 at 03:41:37PM +0000, Ragnar Hafstað wrote:
>
> > actually, perl scripts with \r\n line endings will run just fine in
> > unix/linux.
>
> Indeed, and PL/Perl doesn't care. I just tested several PLs with
> PostgreSQL 8.0.1 on Solaris 9 and here are the results:
>
> PL/pgSQL CRLF ok
> PL/Perl CRLF ok
> PL/Ruby CRLF ok
> PL/Tcl CRLF ok
> PL/Python CRLF fails
> PL/R CRLF fails
>
> Details:
Thanks for the detailed test you ran. This is something I should have
done before spouting off.
So, really, AIUI, one of the "selling points" for each of the
above-mentioned languages is their portability. It would appear to me
that this newline incompatibility ought to be considered a major bug in
python. (Maybe I'm spouting off half-cocked again, though).
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Richard Huxton | 2005-03-16 13:51:51 | Re: 2 questions about types |
| Previous Message | John DeSoi | 2005-03-16 13:14:22 | Re: Installation on XP - Permissions |