4 replies
by shahezadkhan Accepted solution
by tony hopkinson Accepted solution
Upload from what, to what, with what. When do you want to do it.
Query when, with what ....
On top of that storing images in a database is a bad idea. Store a link to them .
Images in database is just a lot of overhead.
You can't query them, so what's the point, just park them on a server somewhere and store a relative path and file name.
by onbliss Accepted solution
Size. Yes. But with the cost of storage reducing, even size of a record or the database becomes less of an issue. The database security & backup features could be useful. The other solution requires a separate backup of the file system.
What other overheads did you have in mind?
by tony hopkinson Accepted solution
depends on how dynamic the images are that one.
Also database consistency checkers go mad on blobs.
If you are maintaining a lot of changes to the images then back up becomes more valuable but the storage gets seriously fragmented.
Then there's page size.
I just don't like it as a solution, the only benefit is single back up. You could call me on round trips, one for the link and one for the image, but a lot of people will optimise on not getting the image by default to avoid the cost of transferring it unless it's specifically requested.
Also if you decide to thread the transfer of the image and the painting of it, you've far fewer potential locking issues.
This discussion is closed to new replies.
Trending Web Development posts
Sort by Trending