Message-Id: <10732.125865@fatcity.com> From: "Koivu, Lisa" Date: Fri, 5 Jan 2001 13:39:26 -0500 Subject: RE: Database design dilemma - not null vs nullable This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C07746.D56C0F3E Content-Type: text/plain What a waste of disk space! Storing spaces instead of leaving a column null? Sounds like storing a bunch of useless garbage to me. -----Original Message----- From: Siv Chelakkara [mailto:Siv.Chelakkara@3cc.co.wayne.mi.us] Sent: Friday, January 05, 2001 1:21 PM To: Multiple recipients of list ORACLE-L Subject: Database design dilemma - not null vs nullable Hi all, We have an outside vendor developing an application, which we will ultimately inherit for maintenance. They are porting this application from a different database platform to Oracle, since we are an Oracle shop. They have decided to make every column in every table a NOT NULL column. They want to implement default values at the database level for every column (' ', 0 and some low date for varchar2, number and date) and then let the application validate and enforce significant data as required. I am looking for opinions on the pros and cons of this type of approach, both from a database and application point of view. Thanks, Siv -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Siv Chelakkara INET: Siv.Chelakkara@3cc.co.wayne.mi.us Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051 San Diego, California -- Public Internet access / Mailing Lists -------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: ListGuru@fatcity.com (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing). ------_=_NextPart_001_01C07746.D56C0F3E Content-Type: text/html Content-Transfer-Encoding: quoted-printable RE: Database design dilemma - not null vs nullable

What a waste of disk space!  Storing spaces = instead of leaving a column null?  Sounds like storing a bunch of = useless garbage to me.


-----Original Message-----
From: Siv Chelakkara [mailto:Siv.Chelakkara@= 3cc.co.wayne.mi.us]
Sent: Friday, January 05, 2001 1:21 PM
To: Multiple recipients of list ORACLE-L
Subject: Database design dilemma - not null vs = nullable


Hi all,

We have an outside vendor developing an application, = which we will ultimately inherit for maintenance.  They are = porting this application from a different database platform to Oracle, = since we are an Oracle shop.  They have decided to make every = column in every table a NOT NULL column.  They want to implement = default values at the database level for every column (' ', 0 and some = low date for varchar2, number and date) and then let the application = validate and enforce significant data as required.  I am looking = for opinions on the pros and cons of this type of approach, both from a = database and application point of view.

Thanks,

Siv


--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: Siv Chelakkara
  INET: = Siv.Chelakkara@3cc.co.wayne.mi.us

Fat City Network Services    -- (858) = 538-5051  FAX: (858) 538-5051
San Diego, = California        -- Public Internet = access / Mailing Lists
---------------------------------------------------------------= -----
To REMOVE yourself from this mailing list, send an = E-Mail message
to: ListGuru@fatcity.com (note EXACT spelling of = 'ListGuru') and in
the message BODY, include a line containing: UNSUB = ORACLE-L
(or the name of mailing list you want to be removed = from).  You may
also send the HELP command for other information =