Skip site navigation (1) Skip section navigation (2)

Re: storing binary data

From: Alex Pilosov <alex(at)acecape(dot)com>
To: Michael Lam <mlam(at)rim(dot)net>
Cc: pgsql-interfaces(at)postgresql(dot)org
Subject: Re: storing binary data
Date: 2001-11-14 00:08:49
Message-ID: Pine.BSO.4.10.10111131908420.23456-100000@spider.pilosoft.com (view raw or flat)
Thread:
Lists: pgsql-interfaces
use bytea. search archives.

On Tue, 13 Nov 2001, Michael Lam wrote:

> I've seen people converting binary data into base64 or uuencode first before
> storing into text files.  Maybe you can do the same and store in a varchar
> field if you like too? Hm...
> 
> -----Original Message-----
> From: Cristovao Dalla Costa [mailto:cbraga(at)bsi(dot)com(dot)br]
> Sent: Tuesday, November 13, 2001 6:10 PM
> To: pgsql-interfaces(at)postgresql(dot)org
> Subject: [INTERFACES] storing binary data
> 
> 
> Hi,
> 
> I'm using libpq to interface my program to postgresql, and I need to store
> some binary data (around 30-40 bytes per element). I'm not sure of the best
> way to do so, since blobs seem awkward. How would you do it? How would you
> insert it in a text field?
> 
> Thanks all,
> 
> Cristovao
> 
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
> 
> http://archives.postgresql.org
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
> message can get through to the mailing list cleanly
> 
> 

-- 
--
Alex Pilosov            | http://www.acedsl.com/home.html
CTO - Acecape, Inc.     | AceDSL:The best ADSL in the world
325 W 38 St. Suite 1005 | (Stealth Marketing Works! :)
New York, NY 10018      |


In response to

pgsql-interfaces by date

Next:From: Joe ConwayDate: 2001-11-14 01:53:27
Subject: Re: storing binary data
Previous:From: Michael LamDate: 2001-11-13 23:31:39
Subject: Re: storing binary data

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group