From: | Zak McGregor <zak(at)mighty(dot)co(dot)za> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Queries across multiple databases (was: SELECT from a table in another database). |
Date: | 2001-05-21 16:50:10 |
Message-ID: | 20010521185010.692bd3c7.zak@mighty.co.za |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
On Mon, 21 May 2001 16:04:25 +0200
Zak McGregor <zak(at)mighty(dot)co(dot)za> wrote:
> I'm not sure whether it is quite the way to do it, but I'd have a
better
> time with things if I could span databases in a single request. Are
> there theoretical problems with spanning databases in a single query?
Is
> it a feature of bad database design & implementation?
I suspect my statement was not so clear. I mean is it a feature of *my*
bad database design & implementation if I am finding it necessary to
contemplate cross-database queries?
Apologies for the vagueness of the original...
Ciao
Zak
--
====================================================================
Zak McGregor
http://www.carfolio.com - Specifications of cars online. Over 7000!
--------------------------------------------------------------------
Of course my password is the same as my pet's name.
My macaw's name was Q47pY!3, but I change it every 90 days.
====================================================================
From | Date | Subject | |
---|---|---|---|
Next Message | Frank Miles | 2001-05-21 16:52:32 | Re: LIKE erratic? or unseen DB corruption? |
Previous Message | Frank Miles | 2001-05-21 16:46:03 | Re: LIKE erratic? or unseen DB corruption? |
From | Date | Subject | |
---|---|---|---|
Next Message | Mikheev, Vadim | 2001-05-21 16:53:35 | RE: Plans for solving the VACUUM problem |
Previous Message | Tom Lane | 2001-05-21 16:45:22 | Is stats update during COPY IN really a good idea? |