DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:content-type;
	b=cenUm5HPgN9pRwJD+XI6KQ6krRyI0hz7/5enzveylfGSGNWOYctxxAUfgfm0oX2Dzu
	8jI1IggMHSvI4cEdAL9ZVOZsDmiPgkLDi6sRvNLR0miJ01oj/ZUPu3G6DD4xasqLQ5tc
	u8pk7jnvFidPqQAapDFNbLWaX3/tGanblG9NY=
MIME-Version: 1.0
In-Reply-To: <20100209074909.GA11838@apartia.fr>
References: <20100209074909.GA11838@apartia.fr>
Date: Tue, 9 Feb 2010 09:34:10 -0200
Message-ID: <5ac667b81002090334u60d9f56dlf06af62e913da547@mail.gmail.com>
Subject: Re: 'image' table with relationships to different objects
From: Michael Lourant <lourant@gmail.com>
To: pgsql-sql@postgresql.org
Content-Type: text/plain; charset=ISO-8859-1

Hi There,

Maybe a table MEDIA_OBJECT with a ID column that will be exported as
FK to other tables and as many columns as media types you want to
store or a single column where you'll store the bytes of your media
file.

Hope it works!

__
Michael Lourant
"Let's warm them all..."


2010/2/9 Louis-David Mitterrand <vindex+lists-pgsql-sql@apartia.org>:
> 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)?
>
> Thanks,
>
> --
> Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-sql
>