| From: | Bruno Wolff III <bruno(at)wolff(dot)to> |
|---|---|
| To: | Igor Maciel Macaubas <igor(at)providerst(dot)com(dot)br> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Database schemas: search_path |
| Date: | 2004-10-14 14:34:32 |
| Message-ID: | 20041014143432.GA25803@wolff.to |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Thu, Oct 14, 2004 at 09:42:45 -0300,
Igor Maciel Macaubas <igor(at)providerst(dot)com(dot)br> wrote:
> Hi all,
>
> I've organized my database design in multiple schemas, and migrated my existing tables to different schemas by using a simple how-to I found in this list history.
> But what I couldn't find was a way to make this schemata fully transparent to my application - which does selects directly to tables instead to schema.table. I know that I can always set the search_path environmnet variable, but I have to do it on each session. I'd like to know if there is a way to make my set search_path persistent on the database, no matter the session.
> I believe that this is supported, but couldn't find out how to make it. Can someone help me?
Use ALTER DATABASE to set per database defaults.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sídar LC | 2004-10-14 15:29:04 | PostgreSQL Tool? |
| Previous Message | Igor Maciel Macaubas | 2004-10-14 12:42:45 | Database schemas: search_path |