This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Hi I should design a scanned document archive . Is it good to store images in database ? (100,000,000 scanned image) or its better to store string which point to image in file system . how about converting all images to SCV and storing them in database?
Images sometimes associated with some record. For example, we have some patients in our DB and there are some x-ray images of each patient associated with the patient. So, there should be some parent-child kind of relationship between the patients and the x-ray images. Now suppose if some user deletes a record of patient then the images belongs to that patient should be deleted with that record, or if not then the patient should not get deleted at all.
Hence if we store images in file system instead of DB, then it would result in lack of integrity. Say, user deletes a patient record, all the image name strings, refering to that patient, are also get deleted, but the actual images are still there. One more case results in real bad. Suppose somebody deletes the image from the file system, but the image name is there in the DB, then the system will look for the actual image and an exception will occur.
Bottomline is store the images in DB, as Jeanne said. [ February 23, 2005: Message edited by: Adeel Ansari ]