From: | "Christoph Zwerschke" <cito(at)online(dot)de> |
---|---|
To: | pgsql-bugs(at)postgresql(dot)org |
Subject: | BUG #5438: Bug/quirk in ascii() function |
Date: | 2010-04-26 08:14:00 |
Message-ID: | 201004260814.o3Q8E0Ne089867@wwwmaster.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
The following bug has been logged online:
Bug reference: 5438
Logged by: Christoph Zwerschke
Email address: cito(at)online(dot)de
PostgreSQL version: 8.0-8.4
Operating system: all
Description: Bug/quirk in ascii() function
Details:
As you would expect,
ascii(cast(' ' as char(1)))
yields 32 in Oracle, SQL Server and MySQL.
However, in PostgreSQL 8.0 to 8.4,
ascii(cast(' ' as char(1))),
ascii(cast(' ' as char))
both give 0. I can imagine why this happens (after all, ' ' is the same as
'' when casted to char), but it is not obvious and what you expect, and
different from the behavior of the other database engines.
With variable length strings, it works as expected,
ascii(' '),
ascii(cast(' ' as varchar(1))),
ascii(cast(' ' as varchar))
all give 32.
I think this quirk should be fixed or at least mentioned in the
documentation of ascii().
From | Date | Subject | |
---|---|---|---|
Next Message | Stefan Kirchev | 2010-04-26 08:16:19 | BUG #5439: Table crash after CLUSTER command |
Previous Message | manohar cr | 2010-04-26 05:29:04 | Re: pgadmin supports on SLES10.3 |