Re^2: BLOBs

It might also be wise to include the following text from the link.

Before we get any further it should be noted that database is not the best place to store a file. Usually when reading or writing to a blob field the entire contents are held in memory. If you are concerned about scalability forget that such a thing called blobs exist. Having said that though it's possible at least with java to pass in an input stream instead of a byte array as the parameter

Examine what is said, not who speaks.

"Efficiency is intelligent laziness." -David Dunham
"Think for yourself!" - Abigail
"Memory, processor, disk in that order on the hardware side. Algorithm, algoritm, algorithm on the code side." - tachyon

Comment on Re^2: BLOBs

Replies are listed 'Best First'.
Re^3: BLOBs by exussum0 (Vicar) on Jun 18, 2004 at 12:49 UTC
Definitely. 100% agreed. Use NFS or something. But sometimes, it's not a bad idea for tiny data, like encryption keys. -- Bart: God, Schmod. I want my monkey-man.	[reply]
Re^3: BLOBs by bodmin (Sexton) on Jun 18, 2004 at 13:00 UTC
Need it to be secure though, don't have any protected folders, so only allow access to files in the db with username and password	[reply]
Re^4: BLOBs by BrowserUk (Patriarch) on Jun 18, 2004 at 13:55 UTC
Hmm. Think about this. If your perl scripts that access your database are in a non-secure file(system), then any DB userids and passwords in them are vulnerable. Is it your intent that a human being (you or a trustee) will always be there to enter the password every time your script runs? Equally, unless the data directories used by your DB are secure, then everything you write into your DB can be read by simply grepping those directories. Examine what is said, not who speaks. "Efficiency is intelligent laziness." -David Dunham "Think for yourself!" - Abigail "Memory, processor, disk in that order on the hardware side. Algorithm, algoritm, algorithm on the code side." - tachyon	[reply] [d/l]