From: | Peter Geoghegan <peter(dot)geoghegan86(at)gmail(dot)com> |
---|---|
To: | Andre Lopes <lopes80andre(at)gmail(dot)com> |
Cc: | postgresql Forums <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Store base64 in database. Use bytea or text? |
Date: | 2011-01-25 22:39:59 |
Message-ID: | AANLkTik46sAOsQ3K=HrZpCh4_NOvLq8LdT9H8JnHdVpk@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 25 January 2011 22:27, Andre Lopes <lopes80andre(at)gmail(dot)com> wrote:
> Hi,
>
> I need to put some images on Base64 in a PostgreSQL database. Wich
> type should I use and what is the difference between using bytea or
> text to store Base64?
I really don't think you want to do that. Base64 is used to make
binary data 7-bit safe for compatibility with legacy systems (i.e. to
embed arbitrary binary data within ASCII). Sometimes people escape
binary data as base64 to store it in their DB, but they typically
store it as bytea. Base64 probably isn't even a particularly good
choice for escaping binary, let alone storing it.
You should just use a generic escaping function. libpq has
PQescapeByteaConn(), for example.
--
Regards,
Peter Geoghegan
From | Date | Subject | |
---|---|---|---|
Next Message | Bill Moran | 2011-01-25 22:46:12 | Re: Store base64 in database. Use bytea or text? |
Previous Message | Dmitriy Igrishin | 2011-01-25 22:39:35 | Re: Store base64 in database. Use bytea or text? |