Alvaro Herrera wrote:
Florian Wunderlich wrote:
- input file in encoding iso-8859-1:
set client_encoding='iso-8859-1';
select upper('ä'), lower('Ä');
(note: the argument to upper is a lower case a umlaut, while the argument to
lower is an upper case a umlaut)
The following bug has been logged online:
Bug reference: 3932
Logged by: Florian Wunderlich
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.6
Operating system: Debian unstable
Description:utf-8 and upper()/lower(): PANIC: ERRORDATA_STACK_SIZE
exceeded
Tom Lane wrote:
"Florian Wunderlich" <[EMAIL PROTECTED]> writes:
The following commands are
used in a file encoded in iso-8859-1:
set client_encoding='utf-8';
select upper('äöü');
Isn't that pilot error, plain and simple? You told the
The following bug has been logged online:
Bug reference: 3316
Logged by: Florian Wunderlich
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.4
Operating system: Linux 2.6.15.6 (debian)
Description:upper() does not convert to upper case on database with
Tom Lane wrote:
>
> Florian Wunderlich <[EMAIL PROTECTED]> writes:
> > So can I be sure that every non-aggregate SELECT on tables joined with
> > unique indexes works, independent of the WHERE or ORDER BY?
>
> I would think that backwards scan on a join mostly doe
FETCH.
So can I be sure that every non-aggregate SELECT on tables joined with
unique indexes works, independent of the WHERE or ORDER BY?
Is anybody working on implementing this functionality?
Thanks,
Florian Wunderlich
---(end of broadcast)---
T
Tom Lane wrote:
>
> [EMAIL PROTECTED] writes:
> > Cursor scrolling broken in 7.3.1 (works in 7.2.1)
>
> That's a fairly sweeping claim.
>
> I have found a bug that explains this problem for the case where the
> cursor retrieves a single row using a unique index. Have you seen it
> happen in any
