Database design questions...

[jizmatik]

Hello all.

Quick question for advice.

I am a photo enthusiast. I want to have a database driven image gallery that will be easily updateable. Now I have a database design question.

My first inclination is to have a database with many tables. 1 main table for the series info, data which only needs to be recorded once and a table for each series containing path info etc.

I thought having one table for all my images might be cumbersome since I have many series for a particular year which are updated frequently. Hence if I wanted to add entries for a series whose end ran next to another series entry's beginning I would have to push down the records potentially changing the unique id...?

Thoughts, please?

[planetsim]

Probably only require two/three tables.

Series

seriesid | title |

Images

imageid | seriesid | title | description | imageurl

Quite basic, as you can see seriesid is in both tables so that you can click on a series, and view all images for that.

[jizmatik]

But say when I need to update the images table and I have two active series and I need to add images to both

--seriesId | thumb | full | numId

1 | small/10.jpg | big/10.jpg | 10
--new entries...(conflict with preceding records?)
2 | small/20.jpg | big/20.jpg | 20
--new entries...(conflict with preceding records?)

Well, simply put is it a hassle to add records inbetween other records?

Remember, I want my site easily updateable...thats why I was thinking multiple tables...

Thanks for replying...