Re: Can updating on long raw column be rolled back?

From: Wasim Hamwi <whamwi_at_bright.net>
Date: Sat, 2 Jan 1999 23:45:29 -0800
Message-ID: <76msii$ivl$1@cletus.bright.net>

Currently , where I work, we have similar situation but we have engineering drawing not images. We have stored all the drawings on separate files ( not into the database) and we have a pointer to go and get the drawing every time someone query the database.

This might be slower, but it will safe you a lot of headache, I am talking about fragmentation when images get deleted.

Wasim

<22E71DAEC504D111B78100805FFE9DC716CB6AF6_at_PFS21>...
>We are thinking about using Oracle to support a image processing
>system. One intuitive way is to store the image data (around 100k)
>in the long raw column. But, will that cause performance problem?
>The image data is supposed to be frequently updated and modified.
>Whether it is better to store it in files? Does the updating on
>raw column use rollback segment and thus involves lots of overhead?
>Any comment/suggestion is greatly appreciated. Thanks.
>
Received on Sun Jan 03 1999 - 01:45:29 CST