Re: Schemas: status report, call for developers

From: "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au>
To: "Ian Barwick" <barwick(at)gmx(dot)net>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Schemas: status report, call for developers
Date: 2002-05-01 02:15:44
Message-ID: GNELIHDDFBOCMGBFGEFOGEFPCCAA.chriskl@familyhealth.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-interfaces

> produces a result like this:
>
> schema | object
> --------+--------
> public | abc
> foo | abc
> foo | xyz
> bar | xyz
> (4 rows)
>
> How can I restrict the query to the schemas in the
> current search path, i.e. the schema names returned
> by SELECT current_schemas() ?

Now, if we had functions-returning-sets, this would all be easy as all you'd
need to do would be to join it with the function returning the set of
schemas in your search path :)

Chris

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2002-05-01 03:20:22 Re: Schemas: status report, call for developers
Previous Message Christopher Kings-Lynne 2002-05-01 02:09:38 Re: Schemas: status report, call for developers

Browse pgsql-interfaces by date

  From Date Subject
Next Message Tom Lane 2002-05-01 03:20:22 Re: Schemas: status report, call for developers
Previous Message Christopher Kings-Lynne 2002-05-01 02:09:38 Re: Schemas: status report, call for developers