Re: proposal: UTF8 to_ascii function - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: proposal: UTF8 to_ascii function
Date
Msg-id 162867790808110856r12fc64c7od3018aa23fb101b0@mail.gmail.com
Whole thread Raw
In response to Re: proposal: UTF8 to_ascii function  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
2008/8/11 Andrew Dunstan <andrew@dunslane.net>:
>
>
> Pavel Stehule wrote:
>>
>> 2008/8/11 Andrew Dunstan <andrew@dunslane.net>:
>>
>>>
>>> Pavel Stehule wrote:
>>>
>>>>>
>>>>> But what would be the meaning of this?:
>>>>>
>>>>>  to_ascii(bytea, integer)
>>>>>
>>>>>
>>>>>
>>>>
>>>> it's symmetric. Nothing more.
>>>>
>>>>
>>>>
>>>
>>> Symmetric to what? What is the second argument supposed to be?
>>>
>>>
>>
>> postgres=# \df to_ascii
>>                       List of functions
>>   Schema   |   Name   | Result data type | Argument data types
>> ------------+----------+------------------+---------------------
>>  pg_catalog | to_ascii | text             | text
>>  pg_catalog | to_ascii | text             | text, integer
>>  pg_catalog | to_ascii | text             | text, name
>>
>> postgres=# select to_ascii('pavel',8);
>>  to_ascii
>> ----------
>>  pavel
>> (1 row)
>>
>>
>>
>
> Hmm. That's not documented, and I suspect shouldn't be there. Everywhere
> else pretty much that I can think of we pass the encoding as a name, and I
> think we should be consistent about it.
>

I don't need it

regards
Pavel

> cheers
>
> andrew
>


pgsql-hackers by date:

Previous
From: "Ryan Bradetich"
Date:
Subject: Re: Question regarding the database page layout.
Next
From: Zdenek Kotala
Date:
Subject: WIP: New Page API