From: | wsheldah(at)lexmark(dot)com |
---|---|
To: | Alvaro Herrera <alvherre(at)atentus(dot)com> |
Cc: | Aasmund Midttun Godal <postgresql(at)envisity(dot)com>, julio(at)bntsoft(dot)com(dot)br, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Record |
Date: | 2001-10-24 15:42:31 |
Message-ID: | 200110241542.LAA27809@interlock2.lexmark.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
If you're using Perl and the DBD::Pg driver, then you can use bytea without
worrying about escaping anything, since the driver takes care of it.
Alvaro Herrera <alvherre%atentus(dot)com(at)interlock(dot)lexmark(dot)com> on 10/24/2001
10:22:39 AM
To: Aasmund Midttun Godal <postgresql%envisity(dot)com(at)interlock(dot)lexmark(dot)com>
cc: julio%bntsoft(dot)com(dot)br(at)interlock(dot)lexmark(dot)com,
pgsql-general%postgresql(dot)org(at)interlock(dot)lexmark(dot)com (bcc: Wesley
Sheldahl/Lex/Lexmark)
Subject: Re: [GENERAL] Record
On Tue, 23 Oct 2001, Aasmund Midttun Godal wrote:
> I am not sure I understand what you mean. However if you are wanting to store
an image in a table you have 2 options:
>
> 1. bytea fields.
> 2. large objects.
Third option is to encode the image (base64?) and then store as text.
It's probably slower (since you have to decode it everytime), uses much
more space, but you don't have to worry about escaping the byte
sequence.
--
Alvaro Herrera (<alvherre[(at)]atentus(dot)com>)
Jajaja! Solo hablaba en serio!
From | Date | Subject | |
---|---|---|---|
Next Message | Keary Suska | 2001-10-24 15:46:59 | Re: PgSendMail, PgLinkPoint, PgMCK (CyberCash) joins |
Previous Message | Mark Coffman | 2001-10-24 15:37:37 | Re: Disable Transaction - plans ? |