Re: invalidly encoded strings

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Jeff Davis <pgsql(at)j-davis(dot)com>, Tatsuo Ishii <ishii(at)postgresql(dot)org>, laurenz(dot)albe(at)wien(dot)gv(dot)at, pgsql-hackers(at)postgresql(dot)org
Subject: Re: invalidly encoded strings
Date: 2007-09-17 00:40:47
Message-ID: 46EDCD0F.8080908@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Tom Lane wrote:
> What I think we'd need to have a complete solution is
>
> convert(text, name) returns bytea
> -- convert from DB encoding to arbitrary encoding
>
> convert(bytea, name, name) returns bytea
> -- convert between any two encodings
>
> convert(bytea, name) returns text
> -- convert from arbitrary encoding to DB encoding
>
> The second and third would need to do a verify step before
> converting, of course.
>
>
>

Is there any reason these functions shouldn't be marked immutable? Also,
I'm wondering if we should give them disambiguating names, rather than
call them all convert.

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2007-09-17 04:02:47 Re: invalidly encoded strings
Previous Message Gregory Stark 2007-09-16 22:00:44 Re: What is happening on buildfarm member dugong

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2007-09-17 01:19:05 Re: HOT synced with HEAD
Previous Message Tom Lane 2007-09-16 19:16:11 Re: HOT synced with HEAD