• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag
 

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Re(2): images in databases
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Re(2): images in databases


  • Subject: Re: Re(2): images in databases
  • From: Lucas Holt <email@hidden>
  • Date: Sat, 26 Feb 2005 22:20:22 -0500

Here is an example:

Say you have a database with images and meta data about those images. (names, descriptions, etc) Lets go further and say they are employees or products. You might have a web based interface on an internet or intranet site and a client side application used in your organization. By putting the images in the database, your client app only needs to speak one protocol to get all of its data! (sql client and opposed to doing sql & http) In this case, you have simplified your application development significantly. Then your client only needs an image library or control to display the image which is fetched along with the other data. You also get one network connection as opposed to two, etc.

Another possible reason would be to avoid limits on image storage. Most file systems have limits on the number of files in a directory or file system. In some cases, its just a scalability issue. Also, you'd have to use relative paths if you store the path in the file system. Case in point, lets say you used an absolute path like /home/myusername/images and then your boss bought an xserve. OSX stores files in /users/myusername/ .. now you need to make a symlink or change all your paths in the database.


On Feb 26, 2005, at 4:15 PM, Robert Snyder wrote:

How is the relationship between the image and an "associated string &
foreign key" improved by using a blob over a file system path entry that
points to the image? Data bases are good for storing and recovering data,
file systems and file servers, Apache included, are good at storing and
serving files.


I think it really comes down to using the best tool for the job. And I
cannot see where putting an image in a database gets you any benefit--or
conversely any reduction in the efficiency of the data model--over a file
system pointer to an image. But I can see a lot more efficiency in using
a file system and file server for the task of actually serving the file.



____________________________________________

Robert Snyder, Director

Lucas Holt email@hidden ________________________________________________________ FoolishGames.com (Jewel Fan Site) JustJournal.com (Free blogging) FoolishGames.net (Enemy Territory IoM site)

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Follow-Ups:
    • Re: images in databases
      • From: PA <email@hidden>
References: 
 >Re: images in databases (From: LD <email@hidden>)
 >Re(2): images in databases (From: "Robert Snyder" <email@hidden>)

  • Prev by Date: Re: attempt to assign value to unknown key
  • Next by Date: WebObjects-Based Phone Platform?
  • Previous by thread: Re: Re(2): images in databases
  • Next by thread: Re: images in databases
  • Index(es):
    • Date
    • Thread