Chris,
At 10:42 AM 7/30/2006, you wrote:
Starting to build a new schema, and one of the items is image storage
In the past I have always used filesystem storage.
Was wondering if I could get a conversation started on the pros/cons
of database storage verse filesystem
Thanks!
It takes a lot more time to extract the data from the table compared to
just reading it off of the disk and you'll get penalized on a busy server.
So why not do both? Why not just store the images in the database as a
repository and when someone requests an image, display it from the disk. If
the image is not on the disk, then extract it from the table and put it on
the disk. (The disk acts like a cache). The table stores the file name,
image description, blob, file date and an optional checksum. If people are
editing the file on the disk then you will need to store the date the file
was last changed in the table so the database knows it has been updated.
You could even archive different versions of the same picture if you need
to. You can also create a checksum of the image file and store that in the
database so you know if there are duplicate images on the disk under a
different file name.
If you are doing searches on the table other than using a unique key with
"=", you may want to store the blob in a separate table because it will
slow down the searches.
Mike
--
----------------------------------
please respond to the list .. if you need to contact me direct
cgmckeever is the account
prupref.com is the domain
<A href="http://www.prupref.com";>Simply Chicago Real Estate</A>
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
