Date: Tue, 9 Feb 2010 20:41:49 +0100
From: Louis-David Mitterrand <vindex+lists-pgsql-sql@apartia.org>
To: pgsql-sql@postgresql.org
Subject: Re: 'image' table with relationships to different objects
Message-ID: <20100209194149.GA22261@apartia.fr>
Mail-Followup-To: pgsql-sql@postgresql.org
References: <20100209074909.GA11838@apartia.fr>
 <4B714E12.1090207@archonet.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4B714E12.1090207@archonet.com>
User-Agent: Mutt/1.5.20 (2009-06-14)

On Tue, Feb 09, 2010 at 11:59:14AM +0000, Richard Huxton wrote:
> On 09/02/10 07:49, Louis-David Mitterrand wrote:
> >Hello,
> >
> >In my database I have different object types (person, location, event,
> >etc.) all of which can have several images attached.
> >
> >What is the best way to manage a single 'image' table with relationships
> >to (potentially) many different object types while keeping referrential
> >integrity (foreign keys)?
> 
> The "clean" way to do this would be with a number of joining tables:
> 
> images    (img_id, file_name, title ...)
> persons   (psn_id, first_name, last_name, ...)
> locations (loc_id, loc_name, lat, lon, ...)
> events    (evt_id, evt_name, starts_on, ends_on, ...)
> 
> person_images   (psn_id, img_id)
> location_images (loc_id, img_id)
> event_images    (evt_id, img_id)

Thank you Richard, this looks like the best solution. And the view is
handy.

-- 
http://www.critikart.net