Ow Mun Heng wrote:
>> Since it is between PostgreSQL databases,
> actually, it'll be against SQL Servers
Oh, ok, then you will have to use DBI-Link.
dblink is not an option since it only connects to PostgreSQL databases.
Yours,
Laurenz Albe
---(end of broadcast)-
On Fri, 2007-09-07 at 10:16 +0200, Albe Laurenz wrote:
> Ow Mun Heng wrote:
> True, you'll have to write some stuff that does something like:
> - pull the data over from the other database
> - replace the data in the local table
Already doing that currently for some data tables/
> Since it is bet
Ow Mun Heng wrote:
>>> In either of the above, I would like to know which one
>>> is able to help me to like connect to a remote DB, use the
>>> table there and join to a local table in PG so that I
>>> don't have to use DBI to pull and insert those data into
>>> the local PG database.
>>
>> Neithe
I'm confused as to the difference between dblink and dbi-link.
dblink is included in the contrib directory and dbi-link is available
from pgfoundry.
dblink seems like it creates a view of a remote DB and is static, which
means that it needs to be refreshed each time.
dbi-link seems like it uses
On Fri, 2007-09-07 at 00:17 -0500, Erik Jones wrote:
> On Sep 6, 2007, at 10:54 PM, Ow Mun Heng wrote:
>
> > In either of the above, I would like to know which one is able to help
> > me to like connect to a remote DB, use the table there and join to a
> > local table in PG so that I don't have to
On Sep 6, 2007, at 10:54 PM, Ow Mun Heng wrote:
I'm confused as to the difference between dblink and dbi-link.
dblink is included in the contrib directory and dbi-link is available
from pgfoundry.
dblink seems like it creates a view of a remote DB and is static,
which
means that it needs t
