in reply to Handling huge BLOB fields with DBI and MySQL

This seems like an interesting solution and you explain it very clearly here. But honestly, I've very rarely found it necessary to store entire files in the database. Particularly because BLOB handling is one of those database features that varies widely from DBMS to DBMS and any solution I write I know I'll have to support in at least three systems :-)

Instead I store pointers to the files -- filenames -- in the database and let the filesystem do what it does best. The most flexible type of filename stored in the database is a partial one, so the calling program needs to have a parameter/property for the root directory. Other tools (e.g., rsync) have been developed and optimized to take care of the distribution/replication issue for files.

M-x auto-bs-mode

  • Comment on Re: Handling huge BLOB fields with DBI and MySQL

Replies are listed 'Best First'.
Re^2: Handling huge BLOB fields with DBI and MySQL
by Anonymous Monk on Apr 10, 2008 at 16:03 UTC
    I have an irrelevant question in regards to BLOB actually. I recently had to do a migration of a database that contains BLOB field (images), I had a exported .sql file which I imported into the new database. Here comes the problem. The BLOB (image) field was unable to load in the new server, anyone know why that is? I have the exact same codes/files as the old one on the new server...Other fields load fine from the database except the BLOB field. Thanks alot.