Re: postgresql vs mysql

From: brian <brian(at)zijn-digital(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: postgresql vs mysql
Date: 2007-02-22 05:17:35
Message-ID: 45DD276F.5040909@zijn-digital.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Chris wrote:
>
> It's not an oddity.
>
> An empty string is a KNOWN value. You know exactly what that value is -
> it's an empty string.
>
> A NULL is UNKNOWN - it doesn't have a value at all.
>

Just to expand on that (and to drag this thread out a little longer), i
find that a pretty good way to get across this difference is to refer to
it as *the* empty string. I prefer this description because it is
implicit that it is still a string. NULL has no type, regardless of the
column it is inserted into. Thus, the empty string is NOT NULL.

brian

In response to

Browse pgsql-general by date

  From Date Subject
Next Message sangeetha k.s 2007-02-22 05:47:27 what compression is used in on disk bitmap index implementation
Previous Message John Smith 2007-02-22 05:11:13 Re: postgresql vs mysql