From: | "Tim Hart" <tjhart(at)mac(dot)com> |
---|---|
To: | "'Florian G(dot) Pflug'" <fgp(at)phlo(dot)org>, "'Berend Tober'" <btober(at)seaworthysys(dot)com> |
Cc: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Null and Void() - Or, Abandon All Hope Ye Who allow |
Date: | 2006-06-28 15:03:21 |
Message-ID: | 000701c69ac4$00754230$1d3210ac@hartt |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
This reminds me of my favorite Bertrand Russell quote:
"The difference between theory and practice is: in theory there is no
difference, but in practice, there is"
-----Original Message-----
From: pgsql-general-owner(at)postgresql(dot)org
[mailto:pgsql-general-owner(at)postgresql(dot)org] On Behalf Of Florian G. Pflug
Sent: Wednesday, June 28, 2006 8:45 AM
To: Berend Tober
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: [GENERAL] Null and Void() - Or, Abandon All Hope Ye Who allow
Well, yes - as I said, using null values gives you more flexibility. But
still, you _can_ shoot yourself in the foot by using them - that's why
it's still good to know why some people oppose them, even if you don't
share their point of view. But of course, "rm -r $(PGDATA)" is a more
efficient way to shoot yourself in the foot, and will probably harm more
then using null ;-)
greetings, Florian Pflug
---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster
From | Date | Subject | |
---|---|---|---|
Next Message | David Fetter | 2006-06-28 15:08:17 | Re: Null and Void() - Or, Abandon All Hope Ye Who allow NULLs? |
Previous Message | David Fetter | 2006-06-28 14:59:25 | Re: Null and Void() - Or, Abandon All Hope Ye Who allow NULLs? |