| From: | "Dave Page" <dpage(at)pgadmin(dot)org> |
|---|---|
| To: | "Ramasubramanian G" <ramasubramanian(dot)g(at)renaissance-it(dot)com> |
| Cc: | sumaya(at)silvermoongroup(dot)com, pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: dblinks |
| Date: | 2008-05-19 08:22:16 |
| Message-ID: | 937d27e10805190122j4b730148vdc1da2a859389ec1@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
On Mon, May 19, 2008 at 4:06 AM, Ramasubramanian G
<ramasubramanian(dot)g(at)renaissance-it(dot)com> wrote:
> HI Sumaya,
>
> This is the way you have to use dblink. And one more think. To
> excute this query you nedd to have dblink functions installed in your
> database schema.
>
> select * from dblink('YOUR_DB_LINK_NAME','select * from mytable')as
> tmp(column1 datatype,column2 datatype.....)
The OP was using EnterpriseDB's Postgres Plus Advanced Server, which
has Oracle-style dblinks built in. They are not used in the same way
as the PostgreSQL dblink module.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bryce Nesbitt | 2008-05-19 21:48:34 | Supplying a default on read, if a column does not exist in DB |
| Previous Message | Ramasubramanian G | 2008-05-19 03:06:47 | Re: dblinks |