| Server IP : 134.29.175.74 / Your IP : 216.73.216.160 Web Server : nginx/1.10.2 System : Windows NT CST-WEBSERVER 10.0 build 19045 (Windows 10) i586 User : Administrator ( 0) PHP Version : 7.1.0 Disable Function : NONE MySQL : OFF | cURL : ON | WGET : OFF | Perl : OFF | Python : OFF | Sudo : OFF | Pkexec : OFF Directory : C:/nginx/html/MichaelMalz/CST1600/Resources/ |
Upload File : |
<?
// MotherCelkosHeuristics.php
$TRACK = "<b>".basename(__FILE__).'</b> <span class="pv_fl">('.__FILE__.")</span>\n<ol>\n";
ini_set('include_path',ini_get('include_path').PATH_SEPARATOR.$_SERVER['DOCUMENT_ROOT']."/"); // Add the DOCUMENT_ROOT to the include_path.
$skipAuthentication = true;
include('application.phpinc');
include('Course/courseInfo.phpinc');
include('../classInfo.phpinc');
$title = "Mother Celko's Heuristics";
$headTitle = '_CST_ - '.$courseNumber.' '.$courseTitle.' - '.$title;
if ( isset($class['section']) ) {
$pageTitle = $courseNumber.'-'.$class['section'].' '.$courseTitle.'<br>'.$title;
} else {
$pageTitle = $courseNumber.' '.$courseTitle.'<br>'.$title;
}
$pageMenu = 'Course/courseMenu.phpinc';
$js .= ',schedule.js';
include('common/pageHeader.phpinc');
$sectionTitle = 'Mother Celko\'s Heuristics';
include('common/sectionHeader.phpinc');
?>
<ul>
<li>Does the entity table make sense? Can you express the idea of the table in a simple collective or plural noun? To be is to be something in particular; to be everything in general or nothing in particular is to be nothing at all (this is known as the Law of Identity in Greek logic). This is why EAV (<a href="https://en.wikipedia.org/wiki/Entity%E2%80%93attribute%E2%80%93value_model">Entity-attribute-value</a>) does not work – it is everything and anything.</li>
<li>Do you have all the attributes that describe the thing in the table? In each row? The most important leg on a three-legged stool is the leg that is missing.</li>
<li>Are all the columns scalar? Or is a column serving more than one purpose? Did you actually put hat size and shoe size in one column? Or store a CSV list in it?</li>
<li>Do not store computed values, such as (unit_price * order_qty). You can compute these things in VIEWs or computed columns.</li>
<li>Does the relationship table make sense? Can you express the idea of the table in a simple sentence, or even better, a name for the relationship? The relationship is “marriage” and not “man_woman_legal_thing”.</li>
<li>Did you check to see if the relationship is 1:1, 1:m or n:m? Does the relationship have attributes of its own? A marriage has a date and a license number that does not belong to aether the husband or the wife. This is why we don't mind tables that model 1:1 relationships.</li>
<li>Does the entity or relationship have a natural key? If it does, then you absolutely have to model it as the PRIMARY KEY or a UNIQUE constraint. Is there a standard industry identifier for it? Let someone else do all that work for you.</li>
<li>If you have a lot of NULL-able columns, the table is probably not normalized.</li>
<li>The NULLs could be non-related entities or relationships.</li>
<li>Do the NULLs have one and only one meaning in each column?</li>
<li>If you have to change more than one row to update, insert or delete a simple fact, then the table is not normalized.</li>
<li>Did you confuse attributes, entities and values? Would you split the Personnel table into “Male_Personnel” and ”Female_Personnel” by splitting out the sex code? No, sex is an attribute and not an entity. Would you have a column for each shoe size? No, a shoe size is a value and not an attribute.</li>
</ul>
<?
include('common/sectionFooter.phpinc');
include('common/pageFooter.phpinc');
?>