From: | "Mircea Sarbu" <msarbu(at)agora(dot)ro> |
---|---|
To: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Using TEXT columns for binary content |
Date: | 2003-04-21 10:31:14 |
Message-ID: | NDBBLPEDOLMDDGLHIECACECAHNAA.msarbu@agora.ro |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hello,
I work with Postgresql 7.2 using Python and Zope as frontend. I have to deal
with some binary content (just pictures) so I considered the options: BLOB and
BYTEA.
BLOB doesn't works for me (because I have no control on the web hosting
environment).
BYTEA seems to be very slow. So far I know, bytea implies tree steps of
processing: string-literal parser, bytea input function and my own encoding
function (of course, a very lazy one...).
I tried a third way: to use simple TEXT columns for storing the pictures. Using
Python library functions for base64 encoding and decoding everything works fine
(and very fast).
My question is:
There are some hidden drawbacks for this approach? (I don't need any further
processing on the binary content)
Thanks for your advice,
Mircea
From | Date | Subject | |
---|---|---|---|
Next Message | greg | 2003-04-21 13:53:57 | Re: DBI & DBD::Pg processor load |
Previous Message | Chris Gamache | 2003-04-21 08:49:07 | DBI & DBD::Pg processor load |