Skip site navigation (1) Skip section navigation (2)

Re: char(0)

From: Susanne Ebrecht <susanne(at)2ndQuadrant(dot)com>
To: Andreas Pflug <pgadmin(at)pse-consulting(dot)de>
Cc: Thomas Kellerer <spam_eater(at)gmx(dot)net>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: char(0)
Date: 2011-10-18 14:38:37
Message-ID: 4E9D8F6D.6030300@2ndQuadrant.com (view raw or flat)
Thread:
Lists: pgsql-bugs
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:
>>> 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.
>> 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

-- 
Susanne Ebrecht - 2ndQuadrant
PostgreSQL Development, 24x7 Support, Training and Services
www.2ndQuadrant.com


In response to

  • Re: char(0) at 2011-10-17 14:41:24 from Andreas Pflug

Responses

pgsql-bugs by date

Next:From: Kevin GrittnerDate: 2011-10-18 16:44:41
Subject: Re: Tablespace files deleted in continuous run
Previous:From: Robert HaasDate: 2011-10-18 13:32:24
Subject: Re: [v9.2] make_greater_string() does not return a string in some cases

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group