Re: Bytea/Base64 encoders for libpq - interested? - Mailing list pgsql-hackers

From Larry Rosenman
Subject Re: Bytea/Base64 encoders for libpq - interested?
Date
Msg-id 20010904121300.A24138@lerami.lerctr.org
Whole thread Raw
In response to Re: Bytea/Base64 encoders for libpq - interested?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
* Tom Lane <tgl@sss.pgh.pa.us> [010904 12:01]:
> They're pretty ugly, but more importantly they're only suitable if we
> have exactly one conversion function each way.  If we have two, what
> will we call the second one?
> 
> I think it's okay to let the argument type be implicit in the function
> argument list.  Something like text_escaped(bytea) and text_direct(bytea)
> (with inverses bytea_escaped(text) and bytea_direct(text)) might do.
> I'm not totally happy with "direct" to suggest minimum escaping, though.
> Better ideas anyone?
Cooked vs raw? 

LER

> 
>             regards, tom lane
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
>     (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)
> 

-- 
Larry Rosenman                     http://www.lerctr.org/~ler
Phone: +1 972-414-9812                 E-Mail: ler@lerctr.org
US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749


pgsql-hackers by date:

Previous
From: Dave Blasby
Date:
Subject: Re: Bad behaviour when inserting unspecified variable length
Next
From: Tom Lane
Date:
Subject: Re: Bytea/Base64 encoders for libpq - interested?