From: | Alex Pilosov <alex(at)pilosoft(dot)com> |
---|---|
To: | Ben-Nes Michael <miki(at)canaan(dot)co(dot)il> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: store in bytea |
Date: | 2001-08-24 19:17:30 |
Message-ID: | Pine.BSO.4.10.10108241516380.10344-100000@spider.pilosoft.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
What are you using to develop? If perl, DBD::Pg will escape/unescape bytea
data after 0.98 version. (Unescaping is automatic, to escape, you need to
do bind(.., SQL_BINARY)).
-alex
On Fri, 24 Aug 2001, Ben-Nes Michael wrote:
> But Ill have to add double slashes and even more importent I will have to
> unescape every binary data going out of the server, which mean in one of my
> aplication all the Images.
>
> Wont this action be much more heavey then the way I used untill now with
> MySQL (blob) ?
> addslash on insert and ordinary select for output.
>
> Does any one here save his website images on DB and retrive them out on his
> web page ?
>
> > "Ben-Nes Michael" <miki(at)canaan(dot)co(dot)il> writes:
> > > On the theoretical issue, can I use TEXT field to store binary ?
> >
> > TEXT will not handle null (zero) bytes. If you are using a multibyte
> > character set, it will likely also do the wrong thing with byte
> > sequences that are illegal or incomplete multibyte characters.
> >
> > Use BYTEA if you want to store arbitrary byte sequences --- that's what
> > it's for.
> >
> > regards, tom lane
> >
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo(at)postgresql(dot)org
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | tmb | 2001-08-24 19:23:27 | HELP WANTED: Open Source Consultant Programmer wanted for quick project |
Previous Message | J.H.M. Dassen Ray | 2001-08-24 19:11:26 | Re: libpq |