<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Down Home Country Coding With Scott Selikoff and Jeanne Boyarsky &#187; Database</title>
	<atom:link href="http://www.selikoff.net/tag/database/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.selikoff.net</link>
	<description>Java/J2EE Software Development and Technology Discussion Blog</description>
	<lastBuildDate>Thu, 29 Jul 2010 10:47:50 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>clone a postgresql database for testing cleanly</title>
		<link>http://www.selikoff.net/2010/03/28/clone-a-postgresql-database-for-testing-cleanly/</link>
		<comments>http://www.selikoff.net/2010/03/28/clone-a-postgresql-database-for-testing-cleanly/#comments</comments>
		<pubDate>Mon, 29 Mar 2010 03:03:35 +0000</pubDate>
		<dc:creator>Jeanne Boyarsky</dc:creator>
				<category><![CDATA[JDBC]]></category>
		<category><![CDATA[JavaRanch Forum Migration]]></category>
		<category><![CDATA[Database]]></category>
		<category><![CDATA[jforum]]></category>
		<category><![CDATA[postgresql]]></category>

		<guid isPermaLink="false">http://www.selikoff.net/?p=1812</guid>
		<description><![CDATA[I&#8217;m looking at writing integration tests for the back end of JavaRanch&#8216;s JForum install. A few &#8220;pesky&#8221; requirements/constraints Multiple developers all over the word have their own local test databases filled with data in different states.  The tests must work for everyone.  Ideally they won&#8217;t leave data floating around either. The tests must use PostgreSQL.  [...]]]></description>
		<wfw:commentRss>http://www.selikoff.net/2010/03/28/clone-a-postgresql-database-for-testing-cleanly/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Which Database to Start With?</title>
		<link>http://www.selikoff.net/2009/08/26/which-database-to-start-with/</link>
		<comments>http://www.selikoff.net/2009/08/26/which-database-to-start-with/#comments</comments>
		<pubDate>Wed, 26 Aug 2009 06:30:35 +0000</pubDate>
		<dc:creator>Scott Selikoff</dc:creator>
				<category><![CDATA[Database]]></category>
		<category><![CDATA[dbms]]></category>
		<category><![CDATA[education]]></category>
		<category><![CDATA[Java/J2EE]]></category>
		<category><![CDATA[learning]]></category>
		<category><![CDATA[sql]]></category>

		<guid isPermaLink="false">http://www.selikoff.net/blog/?p=1160</guid>
		<description><![CDATA[When people ask me how to learn to use a database or how to write SQL queries, I tell them to pick a database system and immerse themselves in it. In fact that advice goes for a lot of software technologies: just immerse yourself in a language, as programming tutorials are easy to come by [...]]]></description>
		<wfw:commentRss>http://www.selikoff.net/2009/08/26/which-database-to-start-with/feed/</wfw:commentRss>
		<slash:comments>14</slash:comments>
		</item>
		<item>
		<title>The Joy of Null:  Continued</title>
		<link>http://www.selikoff.net/2009/04/16/the-joy-of-null-continued/</link>
		<comments>http://www.selikoff.net/2009/04/16/the-joy-of-null-continued/#comments</comments>
		<pubDate>Thu, 16 Apr 2009 18:10:05 +0000</pubDate>
		<dc:creator>Scott Selikoff</dc:creator>
				<category><![CDATA[Database]]></category>
		<category><![CDATA[Java/J2EE]]></category>
		<category><![CDATA[JDBC]]></category>

		<guid isPermaLink="false">http://www.selikoff.net/blog/?p=875</guid>
		<description><![CDATA[In Part 1 of The Joy of Null I discussed a variety of ways null-equivalent values make it into the software design. Often times, developer laziness or immutability of the database tier drives many developers to insert values that simulate null values, rather than using a database null itself. In this second half, I&#8217;ll talk [...]]]></description>
		<wfw:commentRss>http://www.selikoff.net/2009/04/16/the-joy-of-null-continued/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The Joy of Null</title>
		<link>http://www.selikoff.net/2009/04/07/the-joy-of-null/</link>
		<comments>http://www.selikoff.net/2009/04/07/the-joy-of-null/#comments</comments>
		<pubDate>Tue, 07 Apr 2009 16:56:46 +0000</pubDate>
		<dc:creator>Scott Selikoff</dc:creator>
				<category><![CDATA[Database]]></category>
		<category><![CDATA[Java/J2EE]]></category>
		<category><![CDATA[JDBC]]></category>

		<guid isPermaLink="false">http://www.selikoff.net/blog/?p=852</guid>
		<description><![CDATA[Often in the database world, you do not have all the information needed to create a record. For example, you may have a person&#8217;s full name but not their middle name or initial, or you might be missing their date of birth. In such cases, the recommended solution is to fill that field with a [...]]]></description>
		<wfw:commentRss>http://www.selikoff.net/2009/04/07/the-joy-of-null/feed/</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
		<item>
		<title>Making MySQL Use More Memory:  Part 2</title>
		<link>http://www.selikoff.net/2009/03/26/making-mysql-use-more-memory-part-2/</link>
		<comments>http://www.selikoff.net/2009/03/26/making-mysql-use-more-memory-part-2/#comments</comments>
		<pubDate>Thu, 26 Mar 2009 08:01:48 +0000</pubDate>
		<dc:creator>Scott Selikoff</dc:creator>
				<category><![CDATA[Database]]></category>
		<category><![CDATA[myisam]]></category>
		<category><![CDATA[performance]]></category>

		<guid isPermaLink="false">http://www.selikoff.net/blog/?p=825</guid>
		<description><![CDATA[In a previous article, I discussed how to get the most out of your memory usage in MySQL systems using the InnoDB storage engine. To review, MySQL has overly conservative memory usage by default. Your MySQL instance may be using only a small fraction of the available memory, leading to unnecessarily poor application performance. In [...]]]></description>
		<wfw:commentRss>http://www.selikoff.net/2009/03/26/making-mysql-use-more-memory-part-2/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Why JDBC + JSP = Bad</title>
		<link>http://www.selikoff.net/2009/02/24/why-jdbc-jsp-bad/</link>
		<comments>http://www.selikoff.net/2009/02/24/why-jdbc-jsp-bad/#comments</comments>
		<pubDate>Tue, 24 Feb 2009 17:43:21 +0000</pubDate>
		<dc:creator>Scott Selikoff</dc:creator>
				<category><![CDATA[Accessibility]]></category>
		<category><![CDATA[JDBC]]></category>
		<category><![CDATA[Java/J2EE]]></category>
		<category><![CDATA[JavaRanch Forum Migration]]></category>
		<category><![CDATA[Web]]></category>
		<category><![CDATA[Database]]></category>
		<category><![CDATA[JSP]]></category>

		<guid isPermaLink="false">http://www.selikoff.net/blog/?p=788</guid>
		<description><![CDATA[Over years of moderating at The JavaRanch, I&#8217;ve seen one type of question spring up on a weekly basis: that asked by people who need help with JDBC code inside of Java Server Pages (JSPs). As much as we may want to help this individual fix their particular problem, the overriding thought of &#8220;STOP WHAT [...]]]></description>
		<wfw:commentRss>http://www.selikoff.net/2009/02/24/why-jdbc-jsp-bad/feed/</wfw:commentRss>
		<slash:comments>9</slash:comments>
		</item>
		<item>
		<title>Making MySQL Use More Memory</title>
		<link>http://www.selikoff.net/2009/01/07/making-mysql-use-more-memory/</link>
		<comments>http://www.selikoff.net/2009/01/07/making-mysql-use-more-memory/#comments</comments>
		<pubDate>Wed, 07 Jan 2009 06:59:59 +0000</pubDate>
		<dc:creator>Scott Selikoff</dc:creator>
				<category><![CDATA[Database]]></category>
		<category><![CDATA[innodb]]></category>
		<category><![CDATA[performance]]></category>

		<guid isPermaLink="false">http://www.selikoff.net/blog/?p=708</guid>
		<description><![CDATA[Unlike a lot of database servers, MySQL is strangely conservative (by default) on how much memory it will allocate. If you&#8217;re not careful, you can have 16GB of RAM on your machine with MySQL only using 50MBs, leading to extremely poor performance under heavy load. I know firsthand that navigating MySQL configuration guides can be [...]]]></description>
		<wfw:commentRss>http://www.selikoff.net/2009/01/07/making-mysql-use-more-memory/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>postgresql explain</title>
		<link>http://www.selikoff.net/2008/12/13/postgresql-explain/</link>
		<comments>http://www.selikoff.net/2008/12/13/postgresql-explain/#comments</comments>
		<pubDate>Sat, 13 Dec 2008 21:02:00 +0000</pubDate>
		<dc:creator>Jeanne Boyarsky</dc:creator>
				<category><![CDATA[JDBC]]></category>
		<category><![CDATA[Database]]></category>
		<category><![CDATA[postgresql]]></category>

		<guid isPermaLink="false">http://www.selikoff.net/blog/?p=682</guid>
		<description><![CDATA[I had an opportunity to do some tuning on postgresql and was pleasantly surprised at how smoothly it went. The first thing I did was try to run an &#8220;explain&#8221; on the query under discussion.  (Explain is a tabular or graphical view of the detailed steps the database uses to execute your query.  By knowing [...]]]></description>
		<wfw:commentRss>http://www.selikoff.net/2008/12/13/postgresql-explain/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Memo: Avoid Nested Queries in MySQL at all costs</title>
		<link>http://www.selikoff.net/2008/12/10/memo-avoid-nested-queries-in-mysql-at-all-costs/</link>
		<comments>http://www.selikoff.net/2008/12/10/memo-avoid-nested-queries-in-mysql-at-all-costs/#comments</comments>
		<pubDate>Wed, 10 Dec 2008 15:20:52 +0000</pubDate>
		<dc:creator>Scott Selikoff</dc:creator>
				<category><![CDATA[Database]]></category>
		<category><![CDATA[JDBC]]></category>
		<category><![CDATA[mysql]]></category>
		<category><![CDATA[nested]]></category>
		<category><![CDATA[queries]]></category>

		<guid isPermaLink="false">http://www.selikoff.net/blog/?p=652</guid>
		<description><![CDATA[Some of my readers may be aware that nested subqueries such as &#8220;SELECT * FROM widgets WHERE id IN (SELECT &#8230;)&#8221;, don&#8217;t work all that well in MYSQL. While the syntax is usually correct, the performance issues in practice can be horrendous. This article delves deeper into this issue, and why MySQL performs so poorly [...]]]></description>
		<wfw:commentRss>http://www.selikoff.net/2008/12/10/memo-avoid-nested-queries-in-mysql-at-all-costs/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>Denormalized Databases:  A better example</title>
		<link>http://www.selikoff.net/2008/11/23/denormalized-databases-a-better-example/</link>
		<comments>http://www.selikoff.net/2008/11/23/denormalized-databases-a-better-example/#comments</comments>
		<pubDate>Sun, 23 Nov 2008 09:34:57 +0000</pubDate>
		<dc:creator>Scott Selikoff</dc:creator>
				<category><![CDATA[Database]]></category>
		<category><![CDATA[denormalization]]></category>
		<category><![CDATA[denormalize]]></category>
		<category><![CDATA[normalization]]></category>
		<category><![CDATA[normalize]]></category>

		<guid isPermaLink="false">http://www.selikoff.net/blog/?p=622</guid>
		<description><![CDATA[There were a number of comments about my recent article on the negative effects of too much database normalization so allow me to expand the topic a little more. The most consistent comment I saw was that while many of you agreed with me in principle that too much normalization can lead to poor performance, [...]]]></description>
		<wfw:commentRss>http://www.selikoff.net/2008/11/23/denormalized-databases-a-better-example/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>
