Posted by Gerry Vandermaesen on 04/13/06 16:18

Storing images in a database can be quite appropriate if the record and
the image are considered a single entity.

This way your application doesn't need to bother with storing the
images on the filesystem, and for example deleting them when you delete
or update the record. You also are sure your images don't get deleted
from the filesystem while they are still being referenced in a database
record.

So even if you trade in some DB performance for this design, in some
cases it still can be justified.

fletch wrote:
> > Sure - there are very good reasons for keeping images in the database. I also
> > do it when appropriate.
>
> You can't leave it there! What are they!

[Back to original message]