Message-ID: <3F1C0625.9000606@idigx.com>
Date: Mon, 21 Jul 2003 10:26:29 -0500
From: Thomas Swan <tswan@idigx.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.4) Gecko/20030624
MIME-Version: 1.0
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Bruce Momjian <pgman@candle.pha.pa.us>,
	Peter Eisentraut <peter_e@gmx.net>, Joe Conway <mail@joeconway.com>,
	=?ISO-8859-1?Q?Hans-J=FCrgen_Sch=F6ni?= =?ISO-8859-1?Q?g?=
	<postgres@cybertec.at>, pgsql-hackers@postgresql.org, EG <EG@cybertec.at>
Subject: Re: dblink_ora - a first shot on Oracle ...
References: <200307211339.h6LDdTR00206@candle.pha.pa.us>
	<4455.1058796993@sss.pgh.pa.us>
In-Reply-To: <4455.1058796993@sss.pgh.pa.us>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

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
>  
>