Hello all
just note
9.1 will have a bytea_agg aggregate
regards
Pavel Stehule
2011/12/2 Marti Raudsepp :
> On Fri, Dec 2, 2011 at 16:16, Torsten Zuehlsdorff
> wrote:
>> But i clearly have a missunderstanding of other chars, like umlauts or utf-8
>> chars. This, for example, should return a 'ö
Marti Raudsepp schrieb:
On Fri, Dec 2, 2011 at 16:16, Torsten Zuehlsdorff
wrote:
But i clearly have a missunderstanding of other chars, like umlauts or utf-8
chars. This, for example, should return a 'ö':
# SELECT chr(x'C3B6'::int);
chr
-
쎶
(1 row)
That gives you the Unicode codepoint
2011/12/2 Merlin Moncure :
> On Fri, Dec 2, 2011 at 2:01 PM, Pavel Stehule wrote:
so bytea_agg - one param aggregate has sense
it's very easy to implement it
>>>
>>> yup:
>>>
>>> create aggregate bytea_agg (bytea)
>>> (
>>> sfunc=byteacat,
>>> stype=bytea
>>> );
>>
>> this is work
On Fri, Dec 2, 2011 at 2:01 PM, Pavel Stehule wrote:
>>> so bytea_agg - one param aggregate has sense
>>>
>>> it's very easy to implement it
>>
>> yup:
>>
>> create aggregate bytea_agg (bytea)
>> (
>> sfunc=byteacat,
>> stype=bytea
>> );
>
> this is workaround :)
>
> without a memory preallocati
2011/12/2 Merlin Moncure :
> On Fri, Dec 2, 2011 at 11:15 AM, Pavel Stehule
> wrote:
>> 2011/12/2 Merlin Moncure :
>>> On Fri, Dec 2, 2011 at 10:42 AM, Marti Raudsepp wrote:
Sorry, but AFAICT this makes a mess of encodings and only works by
pure luck. The server thinks it's sending the
On Fri, Dec 2, 2011 at 11:15 AM, Pavel Stehule wrote:
> 2011/12/2 Merlin Moncure :
>> On Fri, Dec 2, 2011 at 10:42 AM, Marti Raudsepp wrote:
>>> Sorry, but AFAICT this makes a mess of encodings and only works by
>>> pure luck. The server thinks it's sending the client LATIN1 text, but
>>> it's ac
2011/12/2 Merlin Moncure :
> On Fri, Dec 2, 2011 at 10:42 AM, Marti Raudsepp wrote:
>> Sorry, but AFAICT this makes a mess of encodings and only works by
>> pure luck. The server thinks it's sending the client LATIN1 text, but
>> it's actually UTF8-encoded and the last decoding step is done by you
On Fri, Dec 2, 2011 at 10:42 AM, Marti Raudsepp wrote:
> Sorry, but AFAICT this makes a mess of encodings and only works by
> pure luck. The server thinks it's sending the client LATIN1 text, but
> it's actually UTF8-encoded and the last decoding step is done by your
> terminal.
yup -- your're ri
On Fri, Dec 2, 2011 at 16:16, Torsten Zuehlsdorff
wrote:
> But i clearly have a missunderstanding of other chars, like umlauts or utf-8
> chars. This, for example, should return a 'ö':
>
> # SELECT chr(x'C3B6'::int);
> chr
> -
> 쎶
> (1 row)
That gives you the Unicode codepoint C3B6, but %C3
On Fri, Dec 2, 2011 at 8:16 AM, Torsten Zuehlsdorff
wrote:
> Damien Churchill schrieb:
>
>
>>> after several attempts I have finally succeeded in developing a
>>> urlencode()
>>> function to encode text correctly like defined in RFC 1738.
>>>
>>> Now i have a big problem: how to decode the text?
>
Damien Churchill schrieb:
after several attempts I have finally succeeded in developing a urlencode()
function to encode text correctly like defined in RFC 1738.
Now i have a big problem: how to decode the text?
Example:
# SELECT urlencode('Hellö World!');
urlencode
-
On 2 December 2011 13:18, Torsten Zuehlsdorff wrote:
> Hello,
>
> after several attempts I have finally succeeded in developing a urlencode()
> function to encode text correctly like defined in RFC 1738.
>
> Now i have a big problem: how to decode the text?
>
> Example:
> # SELECT urlencode('Hellö
Hello,
after several attempts I have finally succeeded in developing a
urlencode() function to encode text correctly like defined in RFC 1738.
Now i have a big problem: how to decode the text?
Example:
# SELECT urlencode('Hellö World!');
urlencode
---
Hell%C3%B6%20
13 matches
Mail list logo
