Galen Boyer wrote:
> On 4 Oct 2004, andrew.mccall_at_gmail.com wrote:
>
>>Hi Folks,
>>
>>I am about to start on a project where I will need to store a
>>large amount of images and details about images. SQL seemed a
>>natural choice for this, but I was a little unsure about how to
>>store the image itself.
>>
>>From reading around I have found that there are two techniques
>>that people normally chose for this sort of work:
>>
>>1) To store everything about the image within the SQL database,
>>and the image itself on a file system. A link to the image in
>>the file system is also stored within the SQL database.
>>
>>2) To store the everything, including the image within the
>> database.
>>
>>I was wondering what people thought about these two techniques,
>>and which they would use.
>
>
> Choose #2. #1 means that you have to maintain two things
> seperately as well as keep those two separate things in synch as
> you maintain them.
>
Recommend the first choice. Several reasons. Major failure of your
database will take days not hours to recover. Harder to move data using
blob type objects and harder to display and use images in a web
environment.
Received on Mon Oct 04 2004 - 18:38:44 CDT
