Comments on: Episode 4: What’s “normal,” really? http://www.sitepoint.com/blogs/2006/12/14/episode-4-whats-normal-really/ Thu, 21 Aug 2008 23:20:07 +0000 http://wordpress.org/?v=2.5 By: xhtmlcoder http://www.sitepoint.com/blogs/2006/12/14/episode-4-whats-normal-really/#comment-129625 xhtmlcoder Tue, 19 Dec 2006 16:10:38 +0000 http://www.sitepoint.com/blogs/2006/12/14/episode-4-whats-normal-really/#comment-129625 They should be 1NF at a minimum if they are in 'database format' but it appeared some were not. Although it may be possible to normalise some of the data. No 4. malformed URL and I assume it is supposed to go: tonto.eia.doe If they are using databases; most people usually create a relational database to at least 3NF if they want integrity. The largest Relational Database I ever did was a College Computer Fault network tracking database. Well, when I opened the monster 77 MB sr19 Access database it looked like they had attempted to separate the data but had not actually added the relationships or fully completed normalisation of several of the tables, since there were missing primary keys, etc. They should be 1NF at a minimum if they are in ‘database format’ but it appeared some were not. Although it may be possible to normalise some of the data.

No 4. malformed URL and I assume it is supposed to go: tonto.eia.doe

If they are using databases; most people usually create a relational database to at least 3NF if they want integrity. The largest Relational Database I ever did was a College Computer Fault network tracking database.

Well, when I opened the monster 77 MB sr19 Access database it looked like they had attempted to separate the data but had not actually added the relationships or fully completed normalisation of several of the tables, since there were missing primary keys, etc.

]]> By: malikyte http://www.sitepoint.com/blogs/2006/12/14/episode-4-whats-normal-really/#comment-128316 malikyte Sun, 17 Dec 2006 23:26:15 +0000 http://www.sitepoint.com/blogs/2006/12/14/episode-4-whats-normal-really/#comment-128316 I'm extremely glad to see the previous comment(s) were erased. Just because one person doesn't understand something does not mean it isn't important to others... I never realized how difficult reverse engineering a schema could be to determine what the actual field names (the only identifiable description, unless I go through the related documentation, if any exist) truly mean. If nothing else, I've learned that using fully descriptive names for fields and tables is important. I'm just going to quickly skim through these. Taking a look at the <strong>Nutritional content of food</strong>'s Access database, I'm <em>thinking</em> that it's in 3rd normal form. There are relationships and even (it appears) lookup tables. Without fully studying the fields and their related information, I won't be sure what form it's in, but I'll assume 3rd. I did not look at the ASCII files, but did see that each file apparently represented a table, so they too would (I assume) be in 3rd normal form. I'm not even sure if the <strong>population demographics</strong> meets the requirements of the first normal form. They are separated by State from the index page, but after that they are simply zipped CSV files (at first glance). I've no idea on the SEC filings... I've also no idea on the gas prices (can't understand Excel being in any form), but the link is pointing incorrectly. :) Juvenile arrest rates, also a spreadsheet... Most of these sites I would probably screenscrape and create my own database schema, using only the information I'd need, dropping anything that seemed unnecessary for the task at hand. Unfortunately, I can't figure out what normal form they're in. :( I’m extremely glad to see the previous comment(s) were erased. Just because one person doesn’t understand something does not mean it isn’t important to others…

I never realized how difficult reverse engineering a schema could be to determine what the actual field names (the only identifiable description, unless I go through the related documentation, if any exist) truly mean. If nothing else, I’ve learned that using fully descriptive names for fields and tables is important.

I’m just going to quickly skim through these. Taking a look at the Nutritional content of food’s Access database, I’m thinking that it’s in 3rd normal form. There are relationships and even (it appears) lookup tables. Without fully studying the fields and their related information, I won’t be sure what form it’s in, but I’ll assume 3rd. I did not look at the ASCII files, but did see that each file apparently represented a table, so they too would (I assume) be in 3rd normal form.

I’m not even sure if the population demographics meets the requirements of the first normal form. They are separated by State from the index page, but after that they are simply zipped CSV files (at first glance).

I’ve no idea on the SEC filings…
I’ve also no idea on the gas prices (can’t understand Excel being in any form), but the link is pointing incorrectly. :)
Juvenile arrest rates, also a spreadsheet…

Most of these sites I would probably screenscrape and create my own database schema, using only the information I’d need, dropping anything that seemed unnecessary for the task at hand. Unfortunately, I can’t figure out what normal form they’re in. :(

]]>