User talk:DerekAsirvadem/Sandbox

Computing Redirect‑class

	This redirect is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing articles
Redirect	This redirect does not require a rating on Wikipedia's content assessment scale.

Databases Stub‑class (inactive)

	This article is within the scope of WikiProject Databases, a project which is currently considered to be inactive.DatabasesWikipedia:WikiProject DatabasesTemplate:WikiProject DatabasesDatabases articles
Stub	This article has been rated as Stub-class on Wikipedia's content assessment scale.

Highest?[edit]

Is this a higher normal form truly? The example simply shows a combination of two attributes in one field, something that wouldn't even pass 1NF if you simply rewrote it as an array stored in a field, which it basically is. Gigs (talk) 05:31, 16 December 2007 (UTC)[reply]

I agree; based on the First normal form article, it's not 1NF, since evilness and eccentricity are two attributes being stuffed into one column. I wonder, what about a table with an “upper bound” column and a “lower bound” column, with the constraint that the upper bound is greater? That seems to have the same problem as the given example (two columns with an interdependent constraint), but would be much simpler (assuming I'm correct that such a two-column constraint violates DKNF). Also the solution is less obvious in this case. (My guess would be that you'd store the total range — upper bound minus lower bound — instead of the upper bound, and say the range must be positive; that'd pass DKNF now, right?) Luke Maurer (talk) 22:00, 21 May 2008 (UTC)[reply]

In my opinion, the example given is flawed. You are both converting to DKNF and changing the data as well. A better example would be that you get two tables: one for millionaires and one for billionaires. That satisfies the DKNF requirement since the keys are unchanged and the domains are now constrained in the tables. Remember: the purpose of DKNF is to split generalized constraints into (testable) Domain constraints and Key constraints. I will add this reason to the page. If no comment arrives in a week or so, I'll change the example to clear it up. RonaldKunenborg (talk) 10:51, 8 July 2009 (UTC)[reply]

Incredulous[edit]

1 The entire article is an insult to knowledge and reason. "DKNF" is the result of persons untrained and inexperienced with the theory and practice (the two are inseparable) of Normalisation, purporting to "normalise" a database.
1.a It is an ad hoc form of "do-the-best-you-can" organisation, but it has no relation to the terms "database" or "normalisation", and thus those terms should not be used to describe it.
1.b Using such terms to describe it demeans those terms, which were established 30 years prior, and remain of value to the educated database professional.
1.c It attempts to obtain some credibility to itself by identifying itself using standard terms.

2 The Normal Forms are progressive: 3NF contains 2NF, 2NF contains 1NF; therefore since "DKNF" is neither a formal progression of 4NF or 5NF (which are currently defined, understood and implemented), its claim to being the "highest" Normal Form is entirely false.

3 Since the process identified does not have 1NF, it is not a Normal Form of an kind; from the description, it is merely a status of a non-standard organisation of data in a database storage facility, with no Integrity save for the "domain constraint" and "key constraint".
3.a Even those are supplied as lay descriptions, not technical definitions, and are thus of no value to anyone seeking to understand them.
3.b It avoids confirmation/denial in relation to established and defined terms.

4 The proposition that "The Boyce-Codd normal form, Third normal form, Fourth normal form and Fifth normal form are special cases of the domain/key normal form" is preposterous for several reasons:
4.a If it were such, then it would be a general case of BCNF, 4NF, and 5NF.
4.b It would therefore be a lower normal form to them
4.c It therefores contradicts itself as being the "highest" normal form.
4.d In any case, since the relation is made to defined terms, it would be a simple matter to define it in technical terms, relating to BCNF, 4NF, and 5NF. Such definitions are absent; only a summary lay description is provided.

5 The examples (both the initial and the suggested "compliant" examples) are so poor and confusing the provide neither an example of the undefined proces of normalising to "DKNF", nor the specific definitive difference between the "non-compliant" and "compliant" versions. That is understandable, since the "dknf" is undefined.

6 The example given does not comply with 1NF; this fact further confirms my assertions re [2], [3] and [4]. It is not a "normal" "form" of any kind.

The rest of the article is marketing hype, and not worthy of specific attention.

At best, "DKNF" is as identified in [1.a]. In fact, it is discussed in educated circles as Don't Know Normal Form.

If Wiki is to be taken seriously as an encyclopedia, we must keep such abject nonsense out of it. DerekAsirvadem (talk) 06:52, 31 August 2009 (UTC)[reply]