| From: | John Taylor <postgres(at)jtresponse(dot)co(dot)uk> |
|---|---|
| To: | Rory Campbell-Lange <rory(at)campbell-lange(dot)net>, pgsql-novice(at)postgresql(dot)org |
| Subject: | Re: make default field entry NULL? |
| Date: | 2002-05-23 09:27:23 |
| Message-ID: | 02052310272302.31556@splash.hq.jtresponse.co.uk |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice |
On Thursday 23 May 2002 10:27, Rory Campbell-Lange wrote:
> I'm just starting out using postgresql in specific and sql in general.
>
> I have a table some of whose fields may not be filled in a normal
> INSERT, but may be needed at some future time.
>
> I am aware that the whole are of NULLs is somewhat controversial, but
> unsure if this means I should implement these in my tables.
Generally NULL means "I don't know what the value is", so that sounds
a good value to use for these.
I'm not sure what you mean by "implementing" NULL.
You don't need to do anything, just don't set the values.
>
> I am driving the databases through perl DBI.
I don't use perl DBI, but I don't think that should make any difference.
JohnT
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rory Campbell-Lange | 2002-05-23 09:27:39 | make default field entry NULL? |
| Previous Message | John Taylor | 2002-05-23 09:10:02 | Re: optimising data load |