On 11/21/05, Claude Schneegans <[EMAIL PROTECTED]> wrote: > >>I wouldn't say that there's no advantage. Having one database with > all the image data could easily be used by two or more servers. > > You can do exactly the same with just files in the servers directory system. > So set up another server with a shared directory for files? That's just one more piece of hardware.
> >> The best solution imho, albeit the largest disk space, would be to have > images stored in the database with caching provided by the file > system. > > Then you would have the images read from the database and cached in the > file system? > So why not simply put them in the file system from the begining? > portability. Keep the original in the database. Need a thumbnail 120x120, generate on the fly and cache on the file system. After umpteen people request different thumbnail sizes, you could flush the cache by deleting a directory. You'll still have the originals in the db. > >>This way, you have your source code backup and you have > your database backup. > > The file system also has back up. Yes, one more backup to maintain > > >>you don't also have to have an image folder backup also. > > Folders and files back up can much more efficient than database backup. > Intelligent system will back up only > files that have been modified. Database back up are most of the time not > that selective. > We backup transactions all of the time here. > Many people beleive that database are some sort of panacea that can > handle everything. > Don't forget that a file system is a much more efficient database system > than any other, > when only files and not their content is involved. Then why is microsoft moving towards a database file system? I think the reasoning is that it's much more 'efficient' to keep your metadata and file data together and not in separate storage mechanisms. I'm not saying that you're not correct in your reasoning. I'm just saying that there are advantages to storing blobs in a database. One of the biggest for me happens to be security. I can easily restrict access to image data since I don't have to also mess with the file systems/web servers security settings also. I can look at a column that's maybe labeled 'restricted' and abort the transfer if it's marked true. How easy would that be with a file system? > > -- > _______________________________________ > REUSE CODE! Use custom tags; > See http://www.contentbox.com/claude/customtags/tagstore.cfm > (Please send any spam to this address: [EMAIL PROTECTED]) > Thanks. > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:224897 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
