Hi All,

>> And for the blobs that contain JPEG and TIFF binary compressed data?
>> *YES* compression can be added *BUT* it has to be selectable rather
>> than enforced?
>
> Compressed BLOBs with JPEG or TIFF data won't hurt too much in the
> scheme Jim suggests. You just loose few CPU cycles on the client. The
> only type of system that might be affected is a web server running on
> the same host with database server. All decompression code will eat
> cycles of the same CPU - same as if we would use BLOB filters.

I also think that compression/decompression on already compressed data wouldn't hurt too much
performance, but we need to measure it to be sure. Beside that a BLOB field doesn't always contain
the same type of "data". Who knows what in the future gets into the blob. Therefore i don't like the
idea that compression should become an option.

Also i would suggest that the compression is not only done on BLOB-data, but on every "large"
data-block for whatever data-type. If the size of the data-block is bigger than size X then perform
compression. Why only for BLOBs, i think this shouldn't be dependend on data-type.

Regards,
Arno Brinkman
ABVisie

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Firebird open source database (based on IB-OE) with many SQL-99 features :
http://www.firebirdsql.org
http://www.firebirdsql.info
http://www.fingerbird.de/
http://www.comunidade-firebird.org/

Support list for Interbase and Firebird users :
firebird-support@yahoogroups.com

Nederlandse firebird nieuwsgroep :
news://newsgroups.firebirdsql.info