| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| 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_01C07747.F3C214A0
Content-Type: text/plain;
charset="iso-8859-1"
Lisa, don't mince words. Tell us how you really feel.
-----Original Message-----
From: Koivu, Lisa [mailto:lkoivu_at_qode.com]
Sent: Friday, January 05, 2001 1:37 PM
To: Multiple recipients of list ORACLE-L
Subject: 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_at_3cc.co.wayne.mi.us
<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.comReceived on Fri Jan 05 2001 - 12:47:28 CST
<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_01C07747.F3C214A0 Content-Type: text/html; charset="iso-8859-1"
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>RE: Database design dilemma - not null vs nullable</TITLE>
<META content="MSHTML 5.50.4134.600" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=236194718-05012001><FONT face=Arial color=#0000ff size=2>Lisa,
don't mince words. Tell us how you really feel.</FONT></SPAN></DIV>
<DIV><SPAN class=236194718-05012001><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=236194718-05012001><FONT face=Arial color=#0000ff size=2>-
Ross</FONT></SPAN></DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader><FONT face="Times New Roman" size=2>-----Original Message-----<BR><B>From:</B> Koivu, Lisa [mailto:lkoivu_at_qode.com]<BR><B>Sent:</B> Friday, January 05, 2001 1:37 PM<BR><B>To:</B> Multiple recipients of list ORACLE-L<BR><B>Subject:</B> RE: Database design dilemma - not null vs nullable<BR><BR></FONT></DIV> <P><FONT size=2>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=2>-----Original Message-----</FONT> <BR><FONT size=2>From: Siv Chelakkara [<A href="mailto:Siv.Chelakkara_at_3cc.co.wayne.mi.us">mailto:Siv.Chelakkara_at_3cc.co.wayne.mi.us</A>]</FONT> <BR><FONT size=2>Sent: Friday, January 05, 2001 1:21 PM</FONT> <BR><FONT size=2>To: Multiple recipients of list ORACLE-L</FONT> <BR><FONT size=2>Subject: Database design dilemma - not null vs nullable</FONT> </P><BR> <P><FONT size=2>Hi all,</FONT> </P> <P><FONT size=2>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=2>Thanks,</FONT> </P> <P><FONT size=2>Siv</FONT> </P><BR> <P><FONT size=2>-- </FONT><BR><FONT size=2>Please see the official ORACLE-L FAQ: <A target=_blank href="http://www.orafaq.com">http://www.orafaq.com</A></FONT> <BR><FONT size=2>-- </FONT><BR><FONT size=2>Author: Siv Chelakkara</FONT> <BR><FONT size=2> INET: Siv.Chelakkara_at_3cc.co.wayne.mi.us</FONT> </P> <P><FONT size=2>Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051</FONT> <BR><FONT size=2>San Diego, California -- Public Internet access / Mailing Lists</FONT> <BR><FONT size=2>--------------------------------------------------------------------</FONT> <BR><FONT size=2>To REMOVE yourself from this mailing list, send an E-Mail message</FONT> <BR><FONT size=2>to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in</FONT> <BR><FONT size=2>the message BODY, include a line containing: UNSUB ORACLE-L</FONT> <BR><FONT size=2>(or the name of mailing list you want to be removed from). You may</FONT> <BR><FONT size=2>also send the HELP command for other information (like subscribing).</FONT>
 |
 |