Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Mailing Lists -> Oracle-L -> 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_at_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_at_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_at_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-printableReceived on Fri Jan 05 2001 - 12:39:26 CST
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3DUS-ASCII">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2650.12">
<TITLE>RE: Database design dilemma - not null vs nullable</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=3D2>What a waste of disk space! Storing spaces =
instead of leaving a column null? Sounds like storing a bunch of = useless garbage to me. </FONT></P>
<BR>
<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Siv Chelakkara [<A =
HREF=3D"mailto:Siv.Chelakkara_at_3cc.co.wayne.mi.us">mailto:Siv.Chelakkara@= 3cc.co.wayne.mi.us</A>]</FONT>
<BR><FONT SIZE=3D2>Sent: Friday, January 05, 2001 1:21 PM</FONT>
<BR><FONT SIZE=3D2>To: Multiple recipients of list ORACLE-L</FONT>
<BR><FONT SIZE=3D2>Subject: Database design dilemma - not null vs =
nullable</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>Hi all,</FONT>
</P>
<P><FONT SIZE=3D2>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. </FONT></P>
<P><FONT SIZE=3D2>Thanks,</FONT>
</P>
<P><FONT SIZE=3D2>Siv</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>-- </FONT>
<BR><FONT SIZE=3D2>Please see the official ORACLE-L FAQ: <A =
HREF=3D"http://www.orafaq.com" = TARGET=3D"_blank">http://www.orafaq.com</A></FONT>
<BR><FONT SIZE=3D2>-- </FONT>
<BR><FONT SIZE=3D2>Author: Siv Chelakkara</FONT>
<BR><FONT SIZE=3D2> INET: =
Siv.Chelakkara_at_3cc.co.wayne.mi.us</FONT>
</P>
<P><FONT SIZE=3D2>Fat City Network Services -- (858) =
538-5051 FAX: (858) 538-5051</FONT>
<BR><FONT SIZE=3D2>San Diego, =
California -- Public Internet = access / Mailing Lists</FONT>
<BR><FONT =
SIZE=3D2>---------------------------------------------------------------= -----</FONT>
<BR><FONT SIZE=3D2>To REMOVE yourself from this mailing list, send an =
E-Mail message</FONT>
<BR><FONT SIZE=3D2>to: ListGuru_at_fatcity.com (note EXACT spelling of =
'ListGuru') and in</FONT>
<BR><FONT SIZE=3D2>the message BODY, include a line containing: UNSUB =
ORACLE-L</FONT>
<BR><FONT SIZE=3D2>(or the name of mailing list you want to be removed =
from). You may</FONT>
<BR><FONT SIZE=3D2>also send the HELP command for other information =
![]() |
![]() |