<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>NULL on Nalar</title>
    <link>https://nalar.dev/tags/null/</link>
    <description>Recent content in NULL on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 03 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/null/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Understand SQL NULL with Three-Valued Logic</title>
      <link>https://nalar.dev/understand-sql-null-with-three-valued-logic/</link>
      <pubDate>Thu, 03 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/understand-sql-null-with-three-valued-logic/</guid>
      <description>&lt;p&gt;&lt;code&gt;NULL&lt;/code&gt; is one of the easiest SQL concepts to recognize and one of the easiest to reason about incorrectly.&lt;/p&gt;&#xA;&lt;p&gt;The problem starts when &lt;code&gt;NULL&lt;/code&gt; is treated as if it were an ordinary value such as &lt;code&gt;0&lt;/code&gt;, an empty string, or the word &lt;code&gt;&amp;quot;unknown&amp;quot;&lt;/code&gt;. It is none of those. In SQL, &lt;code&gt;NULL&lt;/code&gt; represents the absence of a known value, and comparisons involving that absence often produce a third logical result: &lt;strong&gt;UNKNOWN&lt;/strong&gt;.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
