<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>Netvouz / emweb / tag / database</title>
<link>http://netvouz.com/emweb/tag/database?feed=rss</link>
<description>emweb&#39;s bookmarks tagged &quot;database&quot; on Netvouz</description>
<item><title>DATABASE DEBUNKINGS - LINKS</title>
<link>http://www.dbdebunk.com/resources.html</link>
<description>04-28-06 Iterative Software Development 	04-28-06 No Silver Bullet 	4-21-06 Ow, My Unnormalized Head! 	4-14-06 The Wonderful World of XML 	2-17-06 When Your Data Is Stored in XML 	2-3-06 10 Common Design Mistakes 	1-27-12 Why SQL Sucks 	1/20/06 Future of Computing 	12/10/05-Authors Don&#39;t Read 	11/11/05 OTLT and EAV 	11/04/05 Bullshit about RDBMS 	08/26/05 Two big design mistakes 	07/01/05 Iterative Software Development 	5/27/05 Why Significant UML Change is Unlikely 	5/13/05 Is XML the Answer? 	5/13/05 Arrogance &amp; Slashing Slashdot (&amp; MySQL) 	5/6/05 I&#39;m Not Buying In 	04/22/05 Intro Iterative &amp; Narrative Integration 	01/4/05 Is Criticism Unprofessional? 	03/18/05 A Simple Guide to Five Normal Forms 	10/15/04 Systems Software Research is Irrelevant 	10/15/04</description>
<category domain="http://netvouz.com/emweb?category=1259949318034822278"></category>
<author>emweb</author>
<pubDate>Tue, 03 Apr 2007 08:42:50 GMT</pubDate>
</item><item><title>integrity constraints definition</title>
<link>http://www.google.com/search?num=100&amp;hl=en&amp;safe=off&amp;pwst=1&amp;sa=X&amp;oi=spell&amp;resnum=0&amp;ct=result&amp;cd=1&amp;q=integrity+constraints+definition&amp;spell=1</link>
<description>Google Search</description>
<category domain="http://netvouz.com/emweb?category=1259949318034822278"></category>
<author>emweb</author>
<pubDate>Fri, 23 Mar 2007 14:57:13 GMT</pubDate>
</item><item><title>KickJava.com - Java API By Example, From Geeks To Geeks.</title>
<link>http://kickjava.com/</link>
<description>A to Z: JavaDoc &amp; Examples   Daily Java News &amp; Articles   Open Source Projects   Open Source Codes   Free Java Books java.* applet (6) 	awt (94) 	beans (12) 	io (110) lang (275) 	math (15) 	net (44) 	nio (34) rmi (2) 	security (20) 	sql (81) 	text (37) util (292) 			 javax.* accessibility (1) 	activation (2) 	activity 	ce crypto (10) 	ejb (13) 	enterprise 	imageio (7) jms (16) 	mail (26) 	management (1) 	microedition (16) naming (9) 	net (10) 	pim (2) 	power (1) print (15) 	resource (6) 	rmi (1) 	security (21) servlet (53) 	sound (2) 	sql (7) 	swing (165) telephony (7) 	transaction (3) 	tv 	xml (76) javacard.* framework (9) 	security (2) 		 javacardx.* crypto 			 org.* ietf (1) 	omg (11) 	w3c (92) 	xml (27)</description>
<category domain="http://netvouz.com/emweb?category=1259949318034822278"></category>
<author>emweb</author>
<pubDate>Thu, 01 Mar 2007 12:14:58 GMT</pubDate>
</item><item><title>Mark McLaren&#39;s Weblog - JSP, JSTL, XML, XSLT and stuff</title>
<link>http://cse-mjmcl.cse.bris.ac.uk/blog/</link>
<description># accessibility # ajax # aop # apache # applet # autowire # axis # blog # bookmarklets # breadcrumbs # canvas # cas # castor # cms # css # css2.1 # csshack # derby # design # dhtml # dwarf # e4x # ehcache # feedfetcher # firefox # gdata # geotools # geourl # gmaps # gml # google # googleajaxsearch # googlecalendar # googleearth # googlenews # googlesuggest # googlewebapi # gpx # ibatis # ie7 # imap # ioc # jato # java # javascript</description>
<category domain="http://netvouz.com/emweb?category=1259949318034822278"></category>
<author>emweb</author>
<pubDate>Wed, 09 May 2007 11:21:41 GMT</pubDate>
</item><item><title>MySQL Tips: Interesting Things to Know about MySQL</title>
<link>http://souptonuts.sourceforge.net/readme_mysql.htm</link>
<description>TIP 1:     Find out who is doing what, and kill the process if needed.     This example kills Id 657.     mysql&gt; show processlist;     show processlist;     +-----+------+-----------+---------+---------+-------+-------+------------------+     | Id  | User | Host      | db      | Command | Time  | State | Info             |     +-----+------+-----------+---------+---------+-------+-------+------------------+     | 657 | prog | localhost | weather | Sleep   | 28619 |       | NULL             |     | 782 | prog | localhost | weather | Sleep   |   853 |       | NULL             |     | 785 | prog | localhost | NULL    | Query   |     0 | NULL  | show processlist |     +-----+------+-----------+---------+---------+-------+-------+------------------+     3 rows i</description>
<category domain="http://netvouz.com/emweb?category=1259949318034822278"></category>
<author>emweb</author>
<pubDate>Thu, 05 Apr 2007 09:01:04 GMT</pubDate>
</item><item><title>ON DK/NF NORMAL FORM</title>
<link>http://www.dbdebunk.com/page/page/621935.htm</link>
<description>DK/NF is best thought of as a straw man (sorry, straw person).  It was introduced by Ron Fagin in his paper &quot;A Normal Form for Relational Databases that Is Based on Domains and Keys,&quot; ACM TODS 6, No. 3 (September 1981).  As Valdez says (more or less), Fagin defines a relvar R to be in DK/NF if and only if every constraint on R is a logical consequence of what he (Fagin) calls the domain constraints and key constraints on R. Here:   A domain constraint--better called an attribute constraint--is simply a constraint to the effect a given attribute A of R takes its values from some given domain D.  A key constraint is simply a constraint to the effect that a given set A, B, ..., C of R constitutes a key for R.   Thus, if R is in DK/NF, then it is sufficient to</description>
<category domain="http://netvouz.com/emweb?category=1259949318034822278"></category>
<author>emweb</author>
<pubDate>Mon, 02 Apr 2007 09:27:01 GMT</pubDate>
</item><item><title>Proper DB Design</title>
<link>http://oldweb.uwp.edu/academic/mis/baldwin/normal.htm</link>
<description>A Well Designed Relational Database [ Anomalies | NF Overview | Functional Dependence | Multivalued Dependence | Keys ] [ Normal Forms | 1NF | 2NF | 3NF | BCNF | 4NF | 5NF | DKNF | Interrelation Constraints ]</description>
<category domain="http://netvouz.com/emweb?category=1259949318034822278"></category>
<author>emweb</author>
<pubDate>Thu, 05 Apr 2007 08:57:47 GMT</pubDate>
</item><item><title>Relational databases - The untold story - Architect - Database - Builder AU</title>
<link>http://www.builderau.com.au/architect/database/soa/Relational_databases_The_untold_story/0,339024547,320273389,00.htm</link>
<description>Discover the origins of the modern relational data model, how rules were set for relational database theory, and how to put the theory into practice. Trying to use a relational database management system (RDBMS) without applying relational database theory to your design is like trying to drive a standard transmission without using the clutch: You&#39;re not going to get very far. In fact, your application may come to a grinding halt. If you&#39;re lucky, you&#39;ll end up with just an inefficient database. But it could be much worse. You could create a database that erroneously reports data or even destroys data. In this series of articles, you&#39;ll learn how to apply relational rules and, in the process, develop an efficient design that protects the validity of your dat</description>
<category domain="http://netvouz.com/emweb?category=1259949318034822278"></category>
<author>emweb</author>
<pubDate>Tue, 20 Mar 2007 13:04:02 GMT</pubDate>
</item><item><title>Relational databases - Using normal forms to create databases</title>
<link>http://builder.com.com/5100-6388-5029912.html</link>
<description>Go further from here:     * SQL Server tips for working with nested triggers and dump files     * Take part in the latest Builder.com technology use survey     * Increase code reuse with Oracle user-defined aggregate functions</description>
<category domain="http://netvouz.com/emweb?category=1259949318034822278"></category>
<author>emweb</author>
<pubDate>Thu, 22 Mar 2007 15:26:23 GMT</pubDate>
</item><item><title>Rules of Data Normalization</title>
<link>http://www.datamodel.org/NormalizationRules.html</link>
<description>1NF  	Eliminate Repeating Groups - Make a separate table for each set of related attributes, and give each table a primary key. 2NF 	Eliminate Redundant Data - If an attribute depends on only part of a multi-valued key, remove it to a separate table. 3NF 	Eliminate Columns Not Dependent On Key - If attributes do not contribute to a description of the key, remove them to a separate table. BCNF 	Boyce-Codd Normal Form - If there are non-trivial dependencies between candidate key attributes, separate them out into distinct tables. 4NF 	Isolate Independent Multiple Relationships - No table may contain two or more 1:n or n:m relationships that are not directly related. 5NF 	Isolate Semantically Related Multiple Relationships - There may be practical constrains o</description>
<category domain="http://netvouz.com/emweb?category=1259949318034822278"></category>
<author>emweb</author>
<pubDate>Mon, 02 Apr 2007 09:31:29 GMT</pubDate>
</item></channel></rss>