Fellow kirupians, I have a database design and it would make me feel better if I had a 3rd party’s approval before I go forward. The design is for a website that will feature downloadable desktop wallpapers in various resolutions and aspect ratios.
— = “one” relationship
—> = “many” relationship
Here’s the schema:
Each entry in the “image” table will fall under an image set, as defined by the relationship between the “image” table and the “image_set” table. An image set is a collection of images that are all really the same image, but in different resolutions, cropped differently for varying aspect ratios, ect. Each image has one set of dimensions and one aspect ratio (obviously, but just to be consistent with what I said). Each image set however has multiple tags and can fall into multiple categories, hence the need for composite entity tables.
For example, a picture of some mountains has its description and thumbnail image stored in the image_set table, but there might be several versions of it, 3 for different widescreen resolutions, 4 for different 4:3 ratios, several for multiple monitor setups, etc.
The ratings table is greyed out because it’s a feature I plan on implementing later, but still need to consider before I go with the design. I’m actually wondering if the “ratings” table can just be combined with the “image_set” table, since there is only one rating for each image set, and only one image set for each rating, and there aren’t multiple attribute columns (which you shouldn’t have anyway) in either table.
