Re: Storing Files IN a database

I would suggest you change the file directory structure to make it simpler and still store the file link in db. If you store the whole file contents inside the db, the time to "save" and "retrive" would degrade your db performance greatly (although I have not done it practically). I worked on one oracle db and we stored images outside db and store the image file location inside db. It worked pretty good.

Hope this helps.

Guang

In article <8tq931$r30$1_at_nnrp1.deja.com>,   Sean <dolans_at_my-deja.com> wrote:
> Oracle 8.1.6 on Wint 4.0 - Java Options not installed at the moment.
>
> QUESTION: Opinions requested on storing files in the database versus
> as files on the operating system.
>
> Task at Hand: A web server that feeds back requested files. The idea
> at first was to store the files on the operating system, but the
> directory structure became extremely complex to sync it with what was
> in the database (on top of the rights architecture we have designed in
> the dbase). One possible solution we are investigating is to store
 the
> file as a BLOB in the system and ???? (feed it) back to the client.
>
> I am curious on opinions of this approach. I have heard in the PAST
> that it was always best to store a link to the file, but I am curious
> about storage, performance, and ways to stream the file to the user.
>
> Much appreciated,
> Sean Dolan
>
> Sent via Deja.com http://www.deja.com/
> Before you b

Sent via Deja.com http://www.deja.com/
Before you buy. Received on Wed Nov 01 2000 - 21:43:11 CST