X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id EC5D59FA226 for ; Tue, 9 May 2006 06:51:35 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 35928-03 for ; Tue, 9 May 2006 06:51:24 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from svr4.postgresql.org (svr4.postgresql.org [66.98.251.159]) by postgresql.org (Postfix) with ESMTP id 109E89F931D for ; Tue, 9 May 2006 06:51:24 -0300 (ADT) Received: from mail.ringways.co.uk (host-80-193-83-141.static.telewest.net [80.193.83.141]) by svr4.postgresql.org (Postfix) with ESMTP id 558405B00ED for ; Tue, 9 May 2006 09:51:21 +0000 (GMT) Received: from eddie.ringways.co.uk ([10.1.1.115]) by mail.ringways.co.uk with esmtp (Exim 4.61) (envelope-from ) id 1FdOrG-0007Zm-IK; Tue, 09 May 2006 10:50:22 +0100 From: Gary Stainburn Organization: Ringways Garages Ltd To: "Jim C. Nasby" Subject: Re: RFC - multi database/application user authentification Date: Tue, 9 May 2006 10:50:19 +0100 User-Agent: KMail/1.9.1 Cc: pgsql-admin@postgresql.org References: <200605041101.17087.gary.stainburn@ringways.co.uk> <20060504182120.GQ97354@pervasive.com> In-Reply-To: <20060504182120.GQ97354@pervasive.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200605091050.20531.gary.stainburn@ringways.co.uk> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200605/81 X-Sequence-Number: 21613 Hi Jim I have considered your comments and they make good sense. As the 2 existing systems integrate with the new one, they will work more and more closely, so I will work on doing as you suggest. Gary On Thursday 04 May 2006 19:21, Jim C. Nasby wrote: > I think a better question to be asking yourself is: why are you using > seperate databases for all of this? It certainly sounds like all the > activities are related, so ISTM it would make a lot more sense to put > everything in one database and possibly use schemas to seperate things > logically. > > On Thu, May 04, 2006 at 11:01:16AM +0100, Gary Stainburn wrote: > > I have two separate database applications running, one for the initial > > Pre-Delivery preparation of new vehicles, and one for the final taxing > > and delivery to customers. > > > > These two systems were developed independently but are used by the same > > people. Each of these databases has a user table, used for initial > > authentication, and also for logging purposes, i.e. who did what action > > and when. Each user table has as it's primary key an int4, but these > > don't match between the two systems. > > > > I am about to develop a new system to encompass the whole order to > > delivery process which will mean the creation of a third system with a > > third database, user table and authentication process. > > > > What is the best way to develop an authentication method where one > > user-id/password system can be used by three separate databases? > > > > Is it possible to get postgresql to do this cross-database access or > > will I have to handle it in the PHP code? > > -- > > Gary Stainburn > > > > This email does not contain private or confidential material as it > > may be snooped on by interested government parties for unknown > > and undisclosed purposes - Regulation of Investigatory Powers Act, 2000 > > > > ---------------------------(end of broadcast)--------------------------- > > TIP 6: explain analyze is your friend -- Gary Stainburn This email does not contain private or confidential material as it may be snooped on by interested government parties for unknown and undisclosed purposes - Regulation of Investigatory Powers Act, 2000