| From: | PostgreSQL - Hans-Jürgen Schönig <postgres(at)cybertec(dot)at> |
|---|---|
| To: | Susanne Ebrecht <susanne(at)2ndQuadrant(dot)com> |
| Cc: | Pg Bugs <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: char(0) |
| Date: | 2011-10-17 08:18:07 |
| Message-ID: | 53019DA1-1161-473F-A6BF-D9907CB0B5B0@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Oct 17, 2011, at 9:31 AM, Susanne Ebrecht wrote:
> Hello,
>
> I couldn't find that somebody already mentioned it.
>
> PostgreSQL isn't supporting CHAR(0).
>
> An empty string has a length of 0.
>
> CHAR(0) can have two values: NULL and empty string.
>
> In MySQL it is very common to simulate not null boolean
> by using CHAR(0).
>
> This is a little bit annoying on migration topics.
>
> Susanne
hello ....
i would actually see it the other way round.
supporting char(0) is the bug here ...
if somebody used char(0) to simulate boolean not null ... let me not comment on that one for social reasons ;).
regards,
hans
--
Cybertec Schönig & Schönig GmbH
Gröhrmühlgasse 26
A-2700 Wiener Neustadt, Austria
Web: http://www.postgresql-support.de
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2011-10-17 08:30:40 | Re: char(0) |
| Previous Message | Susanne Ebrecht | 2011-10-17 07:31:46 | char(0) |