Re: Image "gallery" design considerations

I'm wondering if there are other similar/better or different ways of thinking about doing this. I'm already using SQL (mysql) to hold the News articles on the site, so I could probably make a table there to hold the images and image data, but I've never personally done that, and then I have to deal with filesystem-based storage vs. storing the images in the database itself as a BLOB.

IMHO you don't want to store the images as BLOB in the database.
What we do here requires us to deal with quite a lot of images.
We even have a separate cluster of machines just dealing with storing and delivering images.

What I would suggest is:

1. Store you pictures in the filesystem.
2. Store the description, title, alt tag, keywords (very important), id etc. in the database.
3. Figure out a way to map the database entry to the actual image file.
We use a generated number as the filename which we store alongside with the vehicle information. But you also could just store the filename with the description in the database, so that you can freely choose your filenames.

Another tip: Think about using templates. A great module would be HTML::Template by Sam Tregar.

Kay

Comment on Re: Image "gallery" design considerations