| From: | mlw <markw(at)mohawksoft(dot)com> |
|---|---|
| To: | Oleg Bartunov <oleg(at)sai(dot)msu(dot)su> |
| Cc: | Joe Conway <joseph(dot)conway(at)home(dot)com>, "Ross J(dot) Reedstrom" <reedstrm(at)rice(dot)edu>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Remote connections? |
| Date: | 2001-12-07 13:40:00 |
| Message-ID: | 3C10C6B0.865669C1@mohawksoft.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
The dblink code is a very cool idea.
It got me thinking, what if, just thinking out load here, it was redesigned as
something a little more grandeous.
Imagine this:
select dblink('select * from table', 'table_name', 'db=oracle.test user=chris
passwd=knight', 1) as t1, dblink('table2_name', 1) as t2
Just something to think about.
The first instance of dblink would take 4 parameters: query, table which it
returns, connect string, and link token.
The second instance of dblink would just take the name of the table which it
returns and a link token.
The cool bit is the notion that the query string could specify different
databases or even .DBF libraries.
Just something to think about.
It would REALLY be great if functions could return multiple tuples!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | mlw | 2001-12-07 14:04:57 | Re: restoring a shadow |
| Previous Message | Christof Petig | 2001-12-07 12:09:49 | Re: pg_dump: Sorted output, referential integrity statements |