From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
Cc: | Jan Urbański <j(dot)urbanski(at)students(dot)mimuw(dot)edu(dot)pl>, PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: proposal: UTF8 to_ascii function |
Date: | 2008-08-11 15:19:13 |
Message-ID: | 48A05871.4030007@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Pavel Stehule wrote:
> 2008/8/11 Andrew Dunstan <andrew(at)dunslane(dot)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.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Decibel! | 2008-08-11 15:19:21 | Re: IN vs EXISTS equivalence |
Previous Message | Pavel Stehule | 2008-08-11 15:04:45 | Re: proposal: UTF8 to_ascii function |