Re: importing images

In article <9665@emory.mathcs.emory.edu>, dccrjc9@bpats (David Stockel) writes: |> > Instead of storing these huge amounts of data inefficiently in the database, |> >why not store the address (pathname) in the database and keep your GIF/RASTER file as an operating system file. This will improve performance. |> >If the picture has to be swapped out with another all u have to do is |> >update the pathname and you are ready to go. |> |> Inefficently? Is there some serious problem that I haven't heard about? |> Last year, I converted a system that was using UNIX files to BLOBs. |> There were no BLOB related performace complaints that I heard about. |> |> The conversion also solved some nagging problems with UNIX file |> permissions and ownership. Handing a file off to another user was a |> real messy process. This was greatly simplified by storing the data |> rather than the path. |> |> Using BLOBs also simplifies backups. All the data is on the same tape. The most crucial point IMHO is that by using BLOBs you can fully benefit from the DB inherent security mechanisms (transactions, noone can accidentially delete your files via "rm -r ...", you can grant read/write priviledges to other users, ... Thats what DBS are made for!!) -- Thomas Weik TH Ilmenau Germany There is a theory which states that if ever anyone discovers exactly what the Universe is for and why it is here, it will instantly disappear and be replaced by something even more bizarre and inexplicable. There is another which states that this has already happened. Douglas Adams: The Restaurant at the End of the Universe