From: | "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com> |
---|---|
To: | Petre Scheie <petre(dot)scheie(at)nextelpartners(dot)com> |
Cc: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: PL/Java (was: stored procedures) |
Date: | 2003-03-13 22:35:23 |
Message-ID: | Pine.LNX.4.33.0303131525420.21667-100000@css120.ihs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, 13 Mar 2003, Petre Scheie wrote:
> My DBA and I looked at the link on using SQL for stored procedures
> (thanks Neil!) and he raised a couple concerns:
>
> 1. In the example given, the query is directed at just one table; he
> says he needs to join multiple tables, and have it return a set. Can PG
> do this?
>
> 2. The docs say this ability to return a set is deprecated and may be
> removed in a future release. Why is that? Has this functionality been
> replaced by something else (better?)
>
> Sorry if these are really dumb questions. We're trying to use pg
> (instead of O or SS) but we're new to it.
Sure, that's no problem. Has this guy read much of the docs yet? it's a
worthy investment of time, and they're quite good:
Main 7.3 docs page:
http://www.postgresql.org/docs/view.php?version=7.3&idoc=0&file=index.html
Here's some marketing bullet points from the programmer's guide in 7.3:
* User programmable and built-in functions
* User extensible types, as well as a rich variety of built-ins
* User definable operators
* User definable aggregates
* Rules
* Triggers
* Procedural Languages:
** PL/pgSQL
** PL/Tcl
** PL/Perl
** PL/Python
** PL/R (coming in 7.3)
It's the best database you've never heard of (before now). :-)
From | Date | Subject | |
---|---|---|---|
Next Message | Jean-Luc Lachance | 2003-03-13 22:36:48 | Re: Function in selection? |
Previous Message | Tom Lane | 2003-03-13 22:23:42 | Re: timestamp 'default' question |