I'd agree with chris..... I've got a ton of data/files in mysql for years now and no problems... The thruput in/out is increadible if you implement the storage handler correctly.
Plus it gives you certain advantages such as security/scalability/etc... With storing the files on disk, the files need to be on, or be accessable by the webserver directly via filesystems... This way you need to connect to a mysql server (ideally a different box) using a username/password.. It's a debate that will go on forever ;) On Sat, 13 Dec 2003, Sime wrote: > Chris Nolan wrote: > > Personally, I would have to disagree. I have just completed a > > year-long > > uni project whereby we built some software that stored massive images > > in InnoDB tables. We found that the performance was (at very worst) > > comparable to the alternative method. > > > > Additionally, this method is better on many levels. You can have a > > sealed server and you protect yourself from users who like playing > > with things (like filenames). > > > > On Sat, 2003-12-13 at 08:13, Neil Watson wrote: > >> > >> I believe the data type you are looking for is blob. However, you > >> would > >> be better off using your row to point to a file located on the hard > >> drive instead of actually in the database. I can't recall the > >> technical details but, your performance will be much better that way. > > I'd agree with Neil. I've never believed in that, surely it's just causing > overhead for MySQL. Surely far better to have the files managed by the file > system? That's what it's there for. > > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
