[KPhotoAlbum] Poll: Estimated parent/child count in your DB.

[Martin Höller]

Am Donnerstag, 29. November 2007 schrieb Tero Tilus:
> 2007-11-29 09:20, Paul Fleischer:
> > But, of course you are correct that it would be more efficient to
> > have a map with less entries (namely parents).
>
> How about a little poll to verify assumptions?
>
> Hi all!  What would (in your DB) be the estimated
>  a) percentage of "parents" (photos having "children") and
>  b) average "child" count per "parent"?

Hm, writing this mail the one-to-many/many-to-many/many-to-one relationship 
hit me again:
I have ~9500 pics in the DB of which ~30 are panoramas which are composed of 
2 to 6 original images. How should I use the master/child relationship 
here? Is the panorama the resulting master or a child? What if i want 
several version of the generated panorama?

The image I want to see in thumbnail browser is definitively a panorama and 
not (one of) the original ones. The originals should be attached to it. So 
should the panorama be the "master"?

On the other hand, if I have a picture which I want to improve using gimp or 
whatever, I would have one "master" with one (or probably several) 
derived "child/children".

So I guess for my use a many-to-many relation whould be a must! Am I missing 
something here?

Comments?

- martin
-- 
Martin Höller                   | martin.hoeller at xss.co.at
*x Software + Systeme           | http://www.xss.co.at/
Karmarschgasse 51/2/20          | Tel: +43-1-6060114-30
A-1100 Vienna, Austria          | Fax: +43-1-6060114-71
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kphotoalbum/attachments/20071129/0b76f7d0/attachment.sig>