X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id C55D1D1DC96 for ; Thu, 22 Apr 2004 06:50:11 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 72131-06 for ; Thu, 22 Apr 2004 06:50:06 -0300 (ADT) Received: from anchor-post-37.mail.demon.net (anchor-post-36.mail.demon.net [194.217.242.86]) by svr1.postgresql.org (Postfix) with ESMTP id 558AAD1D2AA for ; Thu, 22 Apr 2004 06:50:04 -0300 (ADT) Received: from mwynhau.demon.co.uk ([193.237.186.96] helo=mainbox.archonet.com) by anchor-post-37.mail.demon.net with esmtp (Exim 3.35 #1) id 1BGaqK-0008bQ-0b; Thu, 22 Apr 2004 10:50:05 +0100 Received: from client17.archonet.com (client17.archonet.com [192.168.1.17]) by mainbox.archonet.com (Postfix) with ESMTP id 8E6CD167AC; Thu, 22 Apr 2004 10:50:03 +0100 (BST) From: Richard Huxton To: "Becky Alcorn" , Subject: Re: Select from two databases Date: Thu, 22 Apr 2004 10:50:03 +0100 User-Agent: KMail/1.5 References: <007601c42837$8d675bd0$140010ac@baeckea> In-Reply-To: <007601c42837$8d675bd0$140010ac@baeckea> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200404221050.03289.dev@archonet.com> X-Virus-Scanned: by amavisd-new at postgresql.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200404/224 X-Sequence-Number: 17599 On Thursday 22 April 2004 08:00, Becky Alcorn wrote: > Hi, > > I was wondering if there has been any further development on running SQL > statements involving more than one database? We are porting a database > from SQLServer to Postgres and some queries in related applications use > joins on tables that are in different databases. We know we can modify the > code to use dblink to accomplish much the same thing in Postgres. Does > anyone know of a more elegant solution for Postgres than dblink? The standard response to this is to suggest using schemas. Any reason why this won't work in your case? -- Richard Huxton Archonet Ltd