A totally other suggestion is to not store the file in the database, but only a
reference to the file and the location. BLOB’s are hard to handle in backups
and recoveries and also in scripts. And if you have to show the file using a
tool, it is already on the disk. And the application is a little bit different,
but not much.
In the company I work we generate a lot of PDF files that must be stored and
those are kept on seperate disks and when we are deciding to place them on
cheaper storage or new storage is it less a burdance on the system to do that.
Only copy the files, change the reference code, delete the file on the old
location and you are done. While moving BLOBs around is much harder.
It is a suggestion to handle things in different ways then storing it in the
database.
Groetjes,
Wim
On Sat, Mar 19, 2011 at 16:20, Jeff Smith wrote:
Sounds like a good idea to just show the image natively though
