in reply to Image "gallery" design considerations
It sounds like a database would be perfect for this job. Particularly because you seem to want to be able to look at the data from several viewpoints at once -- all "Palm" images, say, or all images one at a time in order, or ... This is the bread and butter of relational databases.
You probably only want to store the textual data in the database. Generally, it's best to leave the files themselves to what deals with them best -- namely, the filesystem. It's more complicated, with far more overhead and possible pitfalls, and very little (if any!) gain, to put the images themselves into the database. It's oh-so much easier to just have a column for "image_url" which one can just spit out, and let the browser handle fetching the image from the webserver.
perl -pe '"I lo*`+$^X$\"$]!$/"=~m%(.*)%s;$_=$1;y^`+*^e v^#$&V"+@( NO CARRIER'
|
|---|