Well - databases are used rather than flatfile for when either - you change the data a lot or you need to search the data.
Now images - even if you change the image every 30 seconds, the overhead of database calls negates any good points there. So I assume most people who store images in databases have to search the binary data for something - so I guess they write some app that converts their ascii search term to binary and then checks the database - very long winded when you've got functions that can do that for flatfile stored images.
Or maybe they just put images in their databases because it sounds clever (in much the same way as IIS server sounds clever
Ricardo - you might have guessed by now that we reccommend storing the image as a flatfile and just saving the path in the database.