Results 1 to 3 of 3
  1. #1
    Join Date
    Sep 2005
    Posts
    23

    to BLOB or not to BLOB

    I am wondering if there is a piece of DB theory which clarifies (at the maximum possible) the pros and cons of storing binary data into a Table as a BLOB.

    To put it simple, why should I put my images as BLOB and not store them in a directory and have a field with TEXT or VARCHAR where to store the link to every file.?

  2. #2
    Join Date
    Sep 2002
    Location
    Sydney, Australia
    Posts
    255
    Consider:
    - do you want recovery (of the blob) and integrated recovery(changes in the db vs changes to the blobs)
    - if the blob is in the db, then program can get at the db and the blob at the same time, in the same way (SQL)

    I make the distinction that the blob is stored in a column, not a table. Eg. Employee Fred has one row and his photo is in the Photo column, like the Address column.

    This is an area where the dbs are quite different, so the db you buy will or will not treat blobs well, easily, fast, etc.

    Cheers
    Derek Asirvadem
    Senior Sybase DBA/Information Architect derekATsoftwaregemsDOTcomDOTau
    Anything worth doing is worth doing Right The First Time
    Spend your money on standards-compliant development or spend 10 times more fixing it

  3. #3
    Join Date
    Jun 2004
    Location
    Arizona, USA
    Posts
    1,848
    Here's an online article discussing this point.
    Lou
    使大吃一惊
    "Lisa, in this house, we obey the laws of thermodynamics!" - Homer Simpson
    "I have my standards. They may be low, but I have them!" - Bette Middler
    "It's a book about a Spanish guy named Manual. You should read it." - Dilbert


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •