pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Hans-Jürgen Schönig <hs@cybertec.at>
To: Joe Conway <mail@joeconway.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: Peter Eisentraut <peter_e@gmx.net>
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 18:15:14 +0200
Message-ID: <3F1C1192.5000205@cybertec.at> (raw)
References: <200307211339.h6LDdTR00206@candle.pha.pa.us>
	<4455.1058796993@sss.pgh.pa.us>
	<3F1BFD36.70200@joeconway.com>

> I think for that very reason (SQL-MED) we need to come to terms with 
> this issue. If/when connections to external data sources is in the 
> backend, you'll have those exact same dependencies. And in fact, we do 
> today: consider '--with-openssl' or '--with-tcl'.
> 
> I had always assumed we would need '--with-oracle', '--with-jdbc',  etc 
> (or whatever you want to call them) to support backend connections to 
> external sources. And this discussion is the very reason I was hesitant 
> to pursue dblink_ora or jdbclink now, because I didn't think people 
> would be comfortable with configure options to support a contrib library.
> 
> Joe

If dblink was a core module I would say that adding the configure stuff 
would be very natural. Since this is contrib stuff I was not that sure 
about configure anymore. We will need additional flags for external data 
sources in the (hopefully) near future so I think we should add it.

Personally I tend to think about a solution like that. dblink has a 
great future and many people simply love it (I cannot think of a 
customer who does not like it - it is a killer feature):

- implement the concepts proposed by Joe on this list yesterday (I am 
talking about the functions dblink should provide)
- add support to configure
- merge dblink with dblink_ora as soon as the changes are ready
- adapt jdbc_link and merge it with dblink
- implement dblink_db2, dblink_csv, dblink_xml, and maybe some others
- leave it in contrib because this way it will be shipped with the core 
distribution and people will use it more frequently

I hope that I will finish the Oracle stuff (named connections, ...) 
within the next 3 days.

	Regards,

		Hans


-- 
Cybertec Geschwinde u Schoenig
Ludo-Hartmannplatz 1/14, A-1160 Vienna, Austria
Tel: +43/2952/30706; +43/664/233 90 75
www.cybertec.at, www.postgresql.at, kernel.cybertec.at





view thread (28+ messages)  latest in thread

Message-ID: <3F1C1192.5000205@cybertec.at>
Permalink:  ../3F1C1192.5000205@cybertec.at/
Also on:    postgresql.org/message-id/3F1C1192.5000205@cybertec.at

 · 

reply

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: hs@cybertec.at, mail@joeconway.com, tgl@sss.pgh.pa.us, pgman@candle.pha.pa.us, peter_e@gmx.net, postgres@cybertec.at, EG@cybertec.at
  Subject: Re: dblink_ora - a first shot on Oracle ...
  In-Reply-To: <3F1C1192.5000205@cybertec.at>

* 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