Using blob fields to store PDFs -- good idea/bad idea?
Database
1
Posts
1
Posters
0
Views
1
Watching
-
Where I work, they have thousands of PDFs used as exhibits at trial. From these they select the pertinent ones for the trial at hand, and off they go. It's a pain every time to find the ones they want, so I plan to write a little app to act as interface and store the attributes of each exhibit for easier searching. My design decision here is whether to store the path and name of the PDF in the database, and then retrieve the PDF when necessary, or to actually store the PDF in the database as a blob. What are the implications of storing the PDFs as blobs? Is there a big performance hit? Once stored, the PDFs won't be edited, so it's just passive storage. Do blobs increase the risk of corruption and data loss?