Re: Bytea/Base64 encoders for libpq - interested?

Where did we leave this?

> On Tue, Aug 28, 2001 at 11:07:32AM +0200, Joerg Hessdoerfer wrote:
> > Hi!
> > 
> > Please find attached some very simple encoders/decoders for bytea and base64.
> > Bytea encoder is very picky about what it leaves unescaped - basically the 
> > base64
> > char set ;-)
> > 
> > Since this seems to be a very poorly documented but much asked-for thing, I 
> > thought
> > you would maybe like to add this code to libpq (so that everyone benefits).
> > 
> > I'm aware that function renames might be necessary, though.
> > If you like, I could make the code fit into libpq, and send diffs.
> > 
> > Any comments/interests?
> 
>  What implement base64 PostgreSQL datetype that use externaly base64 and
> internaly same things as bytea. It prevent FE and parser problems with
> "bad" chars and internaly for data storage save less space than text
> with base64. Of course it doesn't solve a problem with encoding/decoding 
> data in your application to/from base64. May be implement for this
> datetype cast to/from bytea too.
> 
>  SELECT my_bytea::base64 FROM foo;
> 
>  INSERT INTO foo (my_bytea) VALUES ('some_base64_string'::bytea);
> 
>  And you can still fetch all data directly in batea by binary cursor. 
> 
>  Comments?
> 
>         Karel
> -- 
>  Karel Zak  <zakkr@zf.jcu.cz>
>  http://home.zf.jcu.cz/~zakkr/
>  
>  C, PostgreSQL, PHP, WWW, http://docs.linux.cz, http://mape.jcu.cz
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org
> 

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026