Hi !

The tests that I have done show the same result as you get. I thought
it was a problem using JDBC so I did the same thing with a 4GL program
and got the same result. It seems that storing large blobs takes a
long time. I also looked at other databases and found similar problems
noted for them.

If you use a smart blob space (version 9.X) and turn off the logging
it will be a lot faster, but you will sacrifice the benefits that
logging will give. The solution that we are using now is to store the
data in a file in the filesystem and then pick it up using a servlet
that then stores the file in a blobcolumn in the database. From the
user perspective it is very fast to store large objects, and it is
then stored in the database a few seconds later, transaction logging
is used in this case. Of course this method is not a 100 % safe, but
close enough for our purposes.


Regards


Ulf



g.cholakov@isy-dc.com (Georgi Cholakov) wrote in message news:<be9f1956.0410112156.348fcecc@posting.google. com>...
> I created a blobspace and then created the table again, using the
> following command:
>
> CREATE TABLE BLOBTEST
> (
> ID INTEGER PRIMARY KEY,
> BLOBCOL BYTE IN BLOBSPACE1
> )
>
> But the time needed to write data in this column (blobcol) is the same
> as previous, when the blobcol was IN TABLE, not in BLOBSPACE1.
>
> Am I missing something?
>
> Thank you for your time.
> Georgi Cholakov