Stephan Szabo <[EMAIL PROTECTED]> writes:
> This is probably not "broken collation order" but instead how those
> locales are defined.
I'd only consider it "broken" if you get different sort order from
sort(1) under the same locale. Here is an example from Fedora 4
showing that sort(1) has the sa
On Sun, 5 Feb 2006, Martin Pitt wrote:
> Hi PostgreSQL developers!
>
> I recently got the email below and confirmed that I get the same
> broken collation order in de_DE.UTF-8 as the original reporter (who
> probably uses pt_PT.something). It works fine in C, though.
This is probably not "broken
Hi PostgreSQL developers!
I recently got the email below and confirmed that I get the same
broken collation order in de_DE.UTF-8 as the original reporter (who
probably uses pt_PT.something). It works fine in C, though.
System: Debian unstable, according to the reporter the bug does not
happen und
This is a table with just one entry created to test the problem. Should
not have any indexing issues.
I've since isolated the problem to the unescape_bytea function not the
SELECT.
I inserted the same image to a bytea column using base64 encoding, and
extracted it from the table (using base
