Re: images in database

"Nigel J. Andrews" wrote:
> B64 would still require a bytea storage type to avoid any character encoding
> issue between client and server though, right?

I don't think so, since it uses characters from the 7-Bit ASCII set
exclusively and IIRC those map to the same codes in almost every
encoding except EBCDIC (though, I'm not an encoding expert).

What might have slowed down bytea as it would text is TOAST's attempt to
compress the data. As image data usually is compressed already (if not
using PPM or such), this will be a waste of time. For that reason alone,
TOAST offers you to disable the compression attempt on a per attribute
base.

Jan

--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck(at)Yahoo(dot)com #