On 17.10.2011 16:41, Andreas Pflug wrote:
> Am 17.10.11 10:53, schrieb Thomas Kellerer:
>> Susanne Ebrecht, 17.10.2011 09:31:
>>> 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.
>> While not move on to a cleaner approach during the migration and use a
>> "boolean not null"?
> Sounds much too straight forward, not mysql-ish artistic enough...
Depends if you want / are able to touch the application source code or not.
Susanne Ebrecht - 2ndQuadrant
PostgreSQL Development, 24x7 Support, Training and Services
In response to
pgsql-bugs by date
|Next:||From: Kevin Grittner||Date: 2011-10-18 16:44:41|
|Subject: Re: Tablespace files deleted in continuous run|
|Previous:||From: Robert Haas||Date: 2011-10-18 13:32:24|
|Subject: Re: [v9.2] make_greater_string() does not return a string
in some cases|