From: Adrian Klaver <aklaver@comcast.net>
To: pgsql-sql@postgresql.org
Subject: Re: mail alert
Date: Thu, 13 Aug 2009 16:30:41 -0700
Message-ID: <200908131630.41508.aklaver@comcast.net> (raw)
In-Reply-To: <E30C7040DE22624185BAD4093190B54437BE5DB4AE@EX2007-MBX-2.uz.kuleuven.ac.be>
References: <E30C7040DE22624185BAD4093190B54437BE5DB49C@EX2007-MBX-2.uz.kuleuven.ac.be>
<4A821D12.3050500@gmail.com>
<E30C7040DE22624185BAD4093190B54437BE5DB4AE@EX2007-MBX-2.uz.kuleuven.ac.be>
On Wednesday 12 August 2009 6:27:25 am Jan Verheyden wrote:
> Hi,
>
> I got a bit stuck...
> I was looking for a solution for option a)
>
> Maybe I'll first explain the situation a bit more:
>
> I have one database for patient registration
> Another one for image storage
> And a third one for book keeping
> A patient should be registered first before the images are stored, so if
> there is a new line in the second database with an id which does not exist
> yet, it has to be notified in the book keeping database.
>
> Now the questions:
> 1) Can I do this with the inner join (tables subject_id from DB1, pat_id
> from DB2), there it is two different databases 2) Once it is notified in
> the book keeping that is not registered yet, is it best to poll on this
> column to send a warning, or use a trigger??
>
> Thanks!!
>
If at all possible, try to move all that information into schema's of one
database. As it stands now you have a lot of moving parts to keep track of via
external processes. It is possible but you lose transactional support and trust
me that turns into a royal pain.
--
Adrian Klaver
aklaver@comcast.net
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: aklaver@comcast.net
Subject: Re: mail alert
In-Reply-To: <200908131630.41508.aklaver@comcast.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox