| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
| Cc: | harding(dot)ian(at)gmail(dot)com, Christopher Browne <cbbrowne(at)acm(dot)org>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Best Procedural Language? |
| Date: | 2006-08-02 04:45:12 |
| Message-ID: | 20060802044512.GA30546@alvh.no-ip.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Merlin Moncure wrote:
> On 8/1/06, Ian Harding <harding(dot)ian(at)gmail(dot)com> wrote:
> >On 8/1/06, Christopher Browne <cbbrowne(at)acm(dot)org> wrote:
> >> Martha Stewart called it a Good Thing when "Carlo Stonebanks"
> ><cstonebanks(at)nissenfasteners(dot)com> wrote:
> >> > I am interested in finding out a "non-religious" answer to which
> >> > procedural language has the richest and most robust implementation
> >> > for Postgres. C is at the bottom of my list because of how much
> >> > damage runaway code can cause. I also would like a solution which is
> >> > platorm-independent; we develop on Windows but may deploy on Linux.
> >>
> >
> >
> >>
> >> - Doing funky string munging using the SQL functions available in
> >> pl/pgsql is likely to be painful;
> >>
> >> - Doing a lot of DB manipulation in pl/Perl or pl/Tcl or such
> >> requires having an extra level of function manipulations that
> >> won't be as natural as straight pl/pgsql.
> >
> >Another important distinguishing characteristic is whether it supports
> >set returning functions. I think only plpgsql does right now.
>
> and C, and SQL ;)
And PL/Perl (and PL/php but it's still immature.)
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2006-08-02 05:05:11 | Re: Best Procedural Language? |
| Previous Message | Tom Lane | 2006-08-02 04:31:02 | Re: plTcl - how to create proc/function libraries |