Skip site navigation (1) Skip section navigation (2)

Re: Passing multiple rows to a function?

From: Vitaly Belman <vitalyb(at)gmail(dot)com>
To: Michael Fuhr <mike(at)fuhr(dot)org>
Cc: Postgresql Novice <pgsql-novice(at)postgresql(dot)org>
Subject: Re: Passing multiple rows to a function?
Date: 2005-04-24 08:48:57
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-novice
I am aware of the aggregate functions but that's not what I need.
Well, it was a bad example to what I really wanted to do, I guess :(
my bad.

I have a recursive table (id, name, parent_id) and I'd like to return
for a given id all its parents - an example to how to do this is given
However, unlike the example I don't want the function to return all
the parents in a string, but instead I want to use the "set returning
functions" to return a table of all the parent_ids. Now I am just
thinking about how to make it a recursive function.

Ideas will be welcome.

On 4/24/05, Michael Fuhr <mike(at)fuhr(dot)org> wrote:
> On Sun, Apr 24, 2005 at 03:00:55AM +0300, Vitaly Belman wrote:
> >
> > I know that you can pass rows/records to a function but what about a
> > few rows? Is that possible?
> >
> > For example, I'd like to send to a function a number of rows from the
> > "workers" table (e.g "select * from workers where age<10") and the
> > function will return their summed salary.
> See "Aggregate Functions" in the PostgreSQL Tutorial, and again in
> the "Functions and Operators" chapter.  Here are links to documentation
> for the latest version of PostgreSQL:
> If you want to create your own aggregate functions, see "User-Defined
> Aggregates" in the "Extending SQL" chapter and the documentation
> --
> Michael Fuhr

 ICQ: 1912453
 AIM: VitalyB1984
 MSN: tmdagent(at)hotmail(dot)com
 Yahoo!: VitalyBe

In response to

pgsql-novice by date

Next:From: Beto .Date: 2005-04-24 23:08:25
Previous:From: Michael FuhrDate: 2005-04-24 00:21:31
Subject: Re: Passing multiple rows to a function?

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group