From: | "Carlo Stonebanks" <stonec(dot)register(at)sympatico(dot)ca> |
---|---|
To: | "'Jim Nasby'" <decibel(at)decibel(dot)org> |
Cc: | <pgsql-interfaces(at)postgresql(dot)org>, "'PGSQL Hackers'" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: ODBC: how to change search_path in DSN? |
Date: | 2007-01-15 15:14:18 |
Message-ID: | 011d01c738b7$d4092c10$6f05a8c0@Mars |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-interfaces |
Hi Jim,
The solution was to put " set search_path=new_path" in Connection Settings
in the ODBC configuration (on Page 2 of the dialog).
Carlo
-----Original Message-----
From: Jim Nasby [mailto:decibel(at)decibel(dot)org]
Sent: January 14, 2007 10:07 PM
To: Carlo Stonebanks
Cc: pgsql-interfaces(at)postgresql(dot)org; PGSQL Hackers
Subject: Re: [INTERFACES] ODBC: how to change search_path in DSN?
On Dec 19, 2006, at 12:06 PM, Carlo Stonebanks wrote:
> I would like to create an ODBC DSN for a user to export files rom
> Acccess to
> a safe area. Right now, all tables are being dumped to public by
> default.
>
> In order to use the one-click export option for Access, I would
> like to have
> the connection for the ODBC DSN file change the default search_path to
> my_schema (and my_schema only).
>
> After seeing a post on this on another resource, I tried putting
> schema=my_schema in the connection settings text box, but the tables
> appeared in public anyway.
I think your only option is to change the default for the user. IT
would be handy if there was a way to set search_path via
pg_service.conf, though...
--
Jim Nasby jim(at)nasby(dot)net
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2007-01-15 15:21:39 | Re: [PATCHES] [HACKERS] [Fwd: Index Advisor] |
Previous Message | Andrew Dunstan | 2007-01-15 15:13:16 | Re: -f <output file> option for pg_dumpall |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2007-01-15 22:18:20 | Re: BCC55 and libpq 8.2 |
Previous Message | CN | 2007-01-15 12:01:56 | Re: BCC55 and libpq 8.2 |