From: Thomas Swan <tswan@idigx.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: Peter Eisentraut <peter_e@gmx.net>
Cc: Joe Conway <mail@joeconway.com>
Cc: Hans-Jürgen Schönig <postgres@cybertec.at>
Cc: pgsql-hackers@postgresql.org, EG <EG@cybertec.at>
Subject: Re: dblink_ora - a first shot on Oracle ...
Date: Mon, 21 Jul 2003 10:26:29 -0500
Message-ID: <3F1C0625.9000606@idigx.com> (raw)
In-Reply-To: <4455.1058796993@sss.pgh.pa.us>
References: <200307211339.h6LDdTR00206@candle.pha.pa.us>
<4455.1058796993@sss.pgh.pa.us>
On 7/21/2003 9:16 AM, Tom Lane wrote:
>Bruce Momjian <pgman@candle.pha.pa.us> writes:
>
>
>>I don't see the problem.
>>
>>
>
>I tend to agree with Peter: if dblink is going to start depending on
>stuff outside Postgres, it ought to be become a separate project,
>if only to simplify distribution and configuration issues.
>
The ability to optionally link to another library does not necessitate a
functional dependency on it.
>Perhaps it could be split into two parts, a PG-specific part and
>a cross-DBMS part?
>
> regards, tom lane
>
>PS: Has anyone looked any further at the SQL-MED standard? ISTM that's
>where we ought to head in the long run.
>
>---------------------------(end of broadcast)---------------------------
>TIP 4: Don't 'kill -9' the postmaster
>
>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: tswan@idigx.com, tgl@sss.pgh.pa.us, pgman@candle.pha.pa.us, peter_e@gmx.net, mail@joeconway.com, postgres@cybertec.at, EG@cybertec.at
Subject: Re: dblink_ora - a first shot on Oracle ...
In-Reply-To: <3F1C0625.9000606@idigx.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox