Now, for another perspective on this. Is there any pressing reason to store the image in the db? I've never quite understood the reason to store images in a db.
I believe in using a tool for what it was created -- a file system is great for storing files -- let it do its job.
I much rather store in the db the image attributes that I might want to search on, along with an image index as the name of the image, but store the actual image on the file system. I would also create some really simple scheme for limiting the number of images in a given folder (number the folders 0, 1, 2, 3, etc.., and store 0-99.gifs in folder 0, 100-199.gifs in folder 2, etc.). Whatever scheme, just make sure that the OS doesn't have to spin loading or searching through an entire folder. Then use DBI to store various attributes and the name of the image in the db, and just search for that. And use the various file attribute comparison functions to figure out if the image is more recent or now -- a simple timestamp comparison should do.
any way, just another perspective.
In reply to Re: Working with DBI and BLOB
by punkish
in thread Working with DBI and BLOB
by mhearse
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |