| From: | Tino Wildenhain <tino(at)wildenhain(dot)de> |
|---|---|
| To: | Glen Parker <glenebob(at)nwlink(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: postgresql vs mysql |
| Date: | 2007-02-23 20:15:41 |
| Message-ID: | 45DF4B6D.2010807@wildenhain.de |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Glen Parker schrieb:
> Ben wrote:
>> I'm sorry maybe I missed something, but if you don't need NULLs and
>> feel they just add extra work, why don't you just declare all your
>> columns to be not null and have them default to zero or an empty string?
>
> Because I DO need NULLS for non text fields, and I still want NULL to
> compare equal to, say, '' and 0. I don't think you read what I wrote...
>
> Put another way, I would like to redefine NULL to mean BLANK or NOT
> ENTERED. Totally different concept.
Not wise concept, but here you go:
WHERE coalesce(sometimesnull,'') = '' or
WHERE coalesce(sometimesnull,0 ) = 0 ...
Regards
Tino
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2007-02-23 20:20:46 | Re: Password issue revisited |
| Previous Message | Glen Parker | 2007-02-23 20:12:30 | Re: postgresql vs mysql |