From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Jasbinder Singh Bali" <jsbali(at)gmail(dot)com> |
Cc: | "Trevor Talbot" <quension(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: language interface in postgresql |
Date: | 2007-08-15 04:36:16 |
Message-ID: | 23714.1187152576@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
"Jasbinder Singh Bali" <jsbali(at)gmail(dot)com> writes:
> Let me fine tune my question here. What I mean to say is the way we can
> write stored procedures in C, perl etc in Postgres specifying the language
> parameter at the end of stored procedure, compared to that, in SQL Server
> 2000 I've seen SP writing in pure SQL only.
Ah. I thought you were talking about client interface libraries in
different languages, which are surely a dime a dozen. As far as
server-side functions go, we might be unique in offering so many
languages to work in. I think we probably are unique in being so
aggressively agnostic about what the function language is. That's
not necessarily all good, as it's driven us to invent curiosities
like dollar-quoting to avoid having to mesh lexical details of the
function language and the outer SQL language.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Trevor Talbot | 2007-08-15 04:43:53 | Re: language interface in postgresql |
Previous Message | Pavel Stehule | 2007-08-15 04:32:49 | Re: Blobs in Postgresql |