Date: Tue, 16 Nov 2004 19:51:31 +0100
To: pgsql-sql@postgresql.org
Subject: Re: tree structure photo gallery date quiery
References: <200411161129.46131.gary.stainburn@ringways.co.uk>
From: =?iso-8859-15?Q?Pierre-Fr=E9d=E9ric_Caillaud?=
	<lists@boutiquenumerique.com>
Organization: =?iso-8859-15?Q?La_Boutique_Num=E9rique?=
Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-15
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Message-ID: <opshkmn5i0cq72hf@musicbox>
In-Reply-To: <200411161129.46131.gary.stainburn@ringways.co.uk>
User-Agent: Opera M2/7.54 (Linux, build 751)


> I'm looking at the possibility of implementing a photo gallery for my
> web site with a tree structure, something like:

	You don't really want a tree structure, because one day you'll want to  
put the same photo in two galleries. Suppose you take a very interesting  
photo of celery during your trip to china, you might want to create a  
'Trip to China' folder, and also a 'Celery' folder for your other celery  
photos... well, if you don't like vegetables, it also works with people,  
moods, geographic regions, themes, etc. You could define this structure :

	You could then define tables describing themes, and/or keywords, link  
photos with these themes and keywords, and define a folder as either being  
a specific collection of photos, or as a collection of one or several  
themes.

	From a tree, it becomes a bit more like a graph.

	Themes can also be organized and relationed together.

	This opens the path to easy searching and cataloguing ; is not that much  
more difficult to do, and in the end you'll have a much better system.

> How would I go about creating a view to show a) the number of photos in
> a gallery and b) the timestamp of the most recent addition for a
> gallery, so that it interrogates all sub-galleries?

	If you're concerned about performance, you should do this in a  
materialized view updated with triggers. If you can afford a seq scan on  
every time, a few stored procs should do the trick.