<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
	
	>
<channel>
	<title>Comments on: In defence of NULL</title>
	<atom:link href="http://www.kalyr.co.uk/weblog/computing/testing/in-defence-of-null/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.kalyr.co.uk/weblog/computing/testing/in-defence-of-null/</link>
	<description>The blogs of Tim Hall</description>
	<lastBuildDate>Fri, 14 Apr 2017 23:35:42 +0000</lastBuildDate>
		<sy:updatePeriod>hourly</sy:updatePeriod>
		<sy:updateFrequency>1</sy:updateFrequency>
	<generator>https://wordpress.org/?v=3.7.41</generator>
	<item>
		<title>By: John P.</title>
		<link>http://www.kalyr.co.uk/weblog/computing/testing/in-defence-of-null/comment-page-1/#comment-77783</link>
		<dc:creator><![CDATA[John P.]]></dc:creator>
		<pubDate>Wed, 09 Mar 2016 22:58:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.kalyr.co.uk/weblog/?p=15183#comment-77783</guid>
		<description><![CDATA[Usually items are given a reordering policy so you can decide what sort of calculation is done in each case. That allows you to exclude items altogether and manage them manually.

Negative stock can be perfectly feasible just because the warehouse choose to stack up their receipt postings until they have time to do them in a batch, but meanwhile the items are placed ready for picking, which menas they are consumed before being received.

The main use of null is to tell whether a value is a positive input or simply a lack of data. For example, test results where zero is a valid input. If you just have a zero rather than a null, does that mean that the user has not entered anything yet or that they have actually entered a zero? If you use a null then you can tell the difference - a null means they haven&#039;t entered a value yet and zero means that they actually typed zero. That way you can verify if all the results have been entered before proceeding.]]></description>
		<content:encoded><![CDATA[<p>Usually items are given a reordering policy so you can decide what sort of calculation is done in each case. That allows you to exclude items altogether and manage them manually.</p>
<p>Negative stock can be perfectly feasible just because the warehouse choose to stack up their receipt postings until they have time to do them in a batch, but meanwhile the items are placed ready for picking, which menas they are consumed before being received.</p>
<p>The main use of null is to tell whether a value is a positive input or simply a lack of data. For example, test results where zero is a valid input. If you just have a zero rather than a null, does that mean that the user has not entered anything yet or that they have actually entered a zero? If you use a null then you can tell the difference &#8211; a null means they haven&#8217;t entered a value yet and zero means that they actually typed zero. That way you can verify if all the results have been entered before proceeding.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim Hall</title>
		<link>http://www.kalyr.co.uk/weblog/computing/testing/in-defence-of-null/comment-page-1/#comment-77780</link>
		<dc:creator><![CDATA[Tim Hall]]></dc:creator>
		<pubDate>Wed, 09 Mar 2016 15:12:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.kalyr.co.uk/weblog/?p=15183#comment-77780</guid>
		<description><![CDATA[&lt;em&gt;Oh dear, if senior users disagree, projects can go pear-shaped very quickly.&lt;/em&gt;

Can you guess what happened? 

To make matters worse, there was a management turf war going on at our end too, which hardly helped. Then we had a consultant on site who resigned mid-project and began working for the customer the next day.]]></description>
		<content:encoded><![CDATA[<p><em>Oh dear, if senior users disagree, projects can go pear-shaped very quickly.</em></p>
<p>Can you guess what happened? </p>
<p>To make matters worse, there was a management turf war going on at our end too, which hardly helped. Then we had a consultant on site who resigned mid-project and began working for the customer the next day.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PaulE</title>
		<link>http://www.kalyr.co.uk/weblog/computing/testing/in-defence-of-null/comment-page-1/#comment-77779</link>
		<dc:creator><![CDATA[PaulE]]></dc:creator>
		<pubDate>Wed, 09 Mar 2016 14:57:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.kalyr.co.uk/weblog/?p=15183#comment-77779</guid>
		<description><![CDATA[Oh dear, if senior users disagree, projects can go pear-shaped very quickly.

The HR system leaving date is an excellent example for null.

A death date in a family history application opens up the possibility of Null meaning two things - &quot;still alive&quot; or &quot;information not known&quot; (and sometimes it could be either).]]></description>
		<content:encoded><![CDATA[<p>Oh dear, if senior users disagree, projects can go pear-shaped very quickly.</p>
<p>The HR system leaving date is an excellent example for null.</p>
<p>A death date in a family history application opens up the possibility of Null meaning two things &#8211; &#8220;still alive&#8221; or &#8220;information not known&#8221; (and sometimes it could be either).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim Hall</title>
		<link>http://www.kalyr.co.uk/weblog/computing/testing/in-defence-of-null/comment-page-1/#comment-77777</link>
		<dc:creator><![CDATA[Tim Hall]]></dc:creator>
		<pubDate>Wed, 09 Mar 2016 13:17:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.kalyr.co.uk/weblog/?p=15183#comment-77777</guid>
		<description><![CDATA[When you get into forward and backward compatabilties of alternative items, that&#039;s a whole &#039;nother can of worms.  For added horror, try to build a system that can cope with the engineers and the stores managers not being able to agree over what&#039;s compatible and what isn&#039;t.]]></description>
		<content:encoded><![CDATA[<p>When you get into forward and backward compatabilties of alternative items, that&#8217;s a whole &#8216;nother can of worms.  For added horror, try to build a system that can cope with the engineers and the stores managers not being able to agree over what&#8217;s compatible and what isn&#8217;t.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PaulE</title>
		<link>http://www.kalyr.co.uk/weblog/computing/testing/in-defence-of-null/comment-page-1/#comment-77776</link>
		<dc:creator><![CDATA[PaulE]]></dc:creator>
		<pubDate>Wed, 09 Mar 2016 12:52:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.kalyr.co.uk/weblog/?p=15183#comment-77776</guid>
		<description><![CDATA[So, how does the stock system deal with items that are being replaced by an alternative item (i.e. becoming obsolete)?
I would have thought that in itself was enough to justify a re-order Yes/No flag.]]></description>
		<content:encoded><![CDATA[<p>So, how does the stock system deal with items that are being replaced by an alternative item (i.e. becoming obsolete)?<br />
I would have thought that in itself was enough to justify a re-order Yes/No flag.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
