| From: | Neanderthelle Jones <elle(at)view(dot)net(dot)au> | 
|---|---|
| To: | PGSQL Mailing List <pgsql-general(at)postgresql(dot)org> | 
| Subject: | Re: Multidatabase query | 
| Date: | 2009-04-08 13:51:54 | 
| Message-ID: | Pine.LNX.4.64.0904082249330.4359@calypso.view.net.au | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-general | 
On Fri, 27 Mar 2009, Mauro Bertoli wrote:
> SELECT 
>   db1.a.id FROM db1.a 
> UNION
>   db2.b.id FROM db2.b
> 
> Where "db1" is a database and "db2" is another database. "a" is a
> table in database "db1" and "b" is a table in database "db2"
You might be able to create the equivalent of a union by having a
front-end program connect to both databases.  You can have two open
connections and query them in turn and put the union together.
Particularly if it is just a union of keys.
But the essential idea is that the database is the universe of data.
E.g. you want to minimize data redundancy in a db, but you wouldn't
want to do that across databases, because they are different,
independent worlds.  What is the business of one is not the business
of the other.
A query like the above seems to defeat this idea.  What you are
calling databases, or what the other DBMS calls databases, arguably
are not.
--
Elle
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jennifer Trey | 2009-04-08 13:58:11 | Re: PGS Tuning Wizard destroys my login | 
| Previous Message | Radcon Entec | 2009-04-08 13:51:44 | pg_dump/psql: Select a server and automate password |