On Tue, 2007-05-22 at 11:00 +0200, clive wrote: > itoctopus wrote: > > I have tried both, and I tell you that I really felt that the filesystem is > > a more convenient way of doing it. > > > I have to agree, filesystems were after all designed to store files. I > reckon reading a file from disk is much quicker than reading from a > database, maybe only fractionaly though. And databases were created to relate data. So if you're image is "related" to something, then it follows using your naive logic, that the image belongs in the database. It just so happens that database data usually resides on the filesystem, and thus your logical argument is still met. Thus, continuing to follow along this pendantic semantic path, it makes more sense that the image be in the database since more requirements are fulfilled. As I'm sure you can see, this logic has holes in it :) Cheers, Rob. -- .------------------------------------------------------------. | InterJinn Application Framework - http://www.interjinn.com | :------------------------------------------------------------: | An application and templating framework for PHP. Boasting | | a powerful, scalable system for accessing system services | | such as forms, properties, sessions, and caches. InterJinn | | also provides an extremely flexible architecture for | | creating re-usable components quickly and easily. | `------------------------------------------------------------' -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
