Skip site navigation (1) Skip section navigation (2)

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search archives
  Advanced Search

Re: To Blob or Not to Blob? THAT is the question.


  • From: "Josh Goldberg" <josh(at)4dmatrix(dot)com>
  • To: "working4aliving" <working4aliving(at)hotmail(dot)com>, <pgsql-admin(at)postgresql(dot)org>
  • Subject: Re: To Blob or Not to Blob? THAT is the question.
  • Date: Thu, 31 Oct 2002 11:13:34 -0800
  • Message-id: <00c601c28111$9be99980$6e02a8c0@4dmatrix.com> <text/plain>

I'm using blobs for ease of management in a high volume, distribuited content distribution system.  My last version of the application used the filesystem to manage the content, and now that I've moved everything to the database my code (php, perl) is much more compact and easier to manage, which translates to better usability and ease of further development.
  ----- Original Message ----- 
  From: working4aliving 
  To: pgsql-admin(at)postgresql(dot)org 
  Sent: Thursday, October 31, 2002 5:17 AM
  Subject: [ADMIN] To Blob or Not to Blob? THAT is the question.


  I have a java app that (is currently using MYSQL, but we're converting to Postgre soon) references small (62kb) images for viewing on the screens of the app.

  Does anyone have any thoughts on database design that they can share with me that would validate why I would want to put Images into blobs in the database, as opposed to just using the filesystem?  I haven't seen much info on (philosophically speaking, I guess)  pro's and con's of using blobs vs. the filesystem reference to the images, so I don't have much data to make a decision on if blobs for this purpose are a good idea, other than the fact that I feel IMO that maintenance for them would be much easier in the filesystem.

  Thanx in advance.


Home | Main Index | Thread Index

Privacy Policy | About PostgreSQL
Copyright © 1996 – 2012 PostgreSQL Global Development Group