<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Luchiana Dumitrescu on Medium]]></title>
        <description><![CDATA[Stories by Luchiana Dumitrescu on Medium]]></description>
        <link>https://medium.com/@luchianadumitrescu?source=rss-92421d69473e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*7CaYbSVrKGEtSz_I7j9OXA.png</url>
            <title>Stories by Luchiana Dumitrescu on Medium</title>
            <link>https://medium.com/@luchianadumitrescu?source=rss-92421d69473e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 22:17:36 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@luchianadumitrescu/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[COUNT(*) vs COUNT(column): What Are You Actually Counting?]]></title>
            <link>https://code.likeagirl.io/count-vs-count-column-what-are-you-actually-counting-2f4d99547f03?source=rss-92421d69473e------2</link>
            <guid isPermaLink="false">https://medium.com/p/2f4d99547f03</guid>
            <category><![CDATA[women-in-tech]]></category>
            <category><![CDATA[data-analysis]]></category>
            <category><![CDATA[learning-with-analogies]]></category>
            <category><![CDATA[sql]]></category>
            <category><![CDATA[count-sql]]></category>
            <dc:creator><![CDATA[Luchiana Dumitrescu]]></dc:creator>
            <pubDate>Wed, 28 Oct 2026 17:16:14 GMT</pubDate>
            <atom:updated>2026-10-28T17:16:14.017Z</atom:updated>
            <content:encoded><![CDATA[<h4>The case of the empty cinema seats and how the Spider-Man movie helped me explain the difference</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*1alFKzOOi9dwPO4G" /><figcaption>Photo by <a href="https://unsplash.com/@billyborneo?utm_source=medium&amp;utm_medium=referral">Billy Aboulkheir</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>A few weeks ago, I went to the cinema with my partner to watch the brand-new movie, <em>Spider-Man: Brand New Day</em>.</p><p>We were both excited to see it. Well, to be honest, my partner was <strong>way more excited than I was</strong>. He’s a real Spider-Man fan. You know, the kind who actually owns a Spider-Man hoodie. 🕷️</p><p>As for me? I wasn’t expecting that much.</p><p>But by the end of the movie, I had to admit it was worth every minute. Even the slight back pain from sitting in that cinema chair for almost three hours🍿</p><h3>Spider-Man, cinema chair, and SQL Count?</h3><p>For sure, you start wondering what Spider-Man, the cinema chair, and my back pain have to do with our SQL.</p><p>Fair enough, and somehow you caught me. I wanna cry out a bit of my back pain 😅 BUT while I was thinking about that movie night, I realized that a cinema hall is actually a pretty good place to explain one of SQL’s simplest-looking, but pretty overlooked, differences <strong>COUNT(*)</strong> vs <strong>COUNT(COLUMN).</strong></p><p>Somehow, the pain was worth it and helped me shoot 2 rabbits with one bullet: I enjoyed the movies, and the analogy for this article jumped out in my mind. 🐇🐇 (no bunny was hurt while writing this article 😉)</p><p>Now back to the good part 😁</p><p>Imagine you’re the manager of the cinema where the movie is going to be screened, and while you sell the ticket for the movie, someone asks you 2 simple questions:</p><blockquote><strong>→ How many seats are there in the cinema hall where the film will be shown?</strong></blockquote><p>AND</p><blockquote><strong>→ How many seats have already been booked?</strong></blockquote><p>It’s all about the same cinema, same seats, and yet 2 different questions, and how you already guessed we will use <strong>COUNT()</strong> to answer both of them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*DV548vlXXJPEnWC1aVWOww.gif" /></figure><h3>Spider-Man: Break New Day — movie night at the cinema</h3><p>Before going deeper, you, as the manager of the cinema, must know your cinema hall, and for that, before answering these 2 question, let’s take a look at the hall:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DECPc8m_WifZdopJzy-t6g.png" /><figcaption>Image generate by the author using ChatGPT</figcaption></figure><p>As you can see, your system shows you what seats were booked and how many are available for future movie fans. All these details are found in your database in a table called <strong>cinema_hall_1_seats</strong> that have the following structure and data:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UHJGN-ObZUikmb3QntWjwA.png" /></figure><p>So, as we can see, we have the <strong>seat_id</strong> and <strong>ticket_id</strong> that was assigned to the seat. Keep in mind the <strong>ticket_id</strong>column because they will help us do the trick 😋</p><h3><strong>How many seats are there in the cinema hall where the film will be shown?</strong></h3><p>Let’s take our seats and invite<strong>COUNT(*)</strong> on the stage 👏 . As we saw above, our table has a <strong>seat_id</strong> column that contains, as you guessed (somehow I heard you say out loud, do not ask further 😂), the identifier of each seat of this hall.</p><p>But, let’s not go deeper with the uniques and identifiers because it’s not our scope for now (if you’re really curious, you can read more about it 👉<a href="https://code.likeagirl.io/primary-keys-vs-foreign-keys-625175213169"><strong>here</strong></a>👈).</p><p>Going back to our business, it’s time to answer our first question:</p><blockquote><strong>How many seats are there in the cinema hall where the film will be shown?</strong></blockquote><p>Nothing is easier than this, because our <strong>COUNT(*)</strong> is present tonight to help us.</p><pre>SELECT COUNT(*) AS total_seats<br>FROM cinema_hall_1_seats;</pre><p>The result?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/412/1*aHpnu5IRLxCKDsj4ZNHD4Q.png" /></figure><p><strong>15 seats! (A</strong>t least in our little scenario, cuz’ I doubt there’s a cinema hall that small😂)</p><blockquote>Did it matter whether those seats were booked or not?</blockquote><p>Not at all! And that’s because <strong>COUNT(*)</strong> counts every row in your table, regardless of its state (booked or not).</p><p>So as long as the seat is in a row in that table, it gets its moment in the spotlight when the counting begins 🎥</p><blockquote>But wait… what if our cinema manager doesn’t care about the total number of seats?</blockquote><blockquote>What if they only want to know how many seats have already been booked?</blockquote><blockquote>Well, that’s another question to answer to. 👀</blockquote><h3><strong>How many seats have already been booked?</strong></h3><p>That’s the most interesting part for a manager, ‘cuz money talks after all. So, for this, somehow we have to change our tactic, but not our main actor, the <strong>COUNT()</strong> .</p><p>What column tells us that a seat is booked? That’s right, the one we promised to keep in mind, <strong>ticket_id </strong>.</p><pre>SELECT COUNT(ticket_id) AS booked_seats<br>FROM cinema_hall_1_seats;</pre><p>As we saw above, our <strong>ticket_id</strong> column also contains <strong>NULL </strong>values, but what do you think? Will <strong>COUNT(ticket_id)</strong> count those <strong>NULL </strong>values, or will it simply ignore them?</p><p>It will ignore them completely! 😎 That’s the beauty of: it counts only the values that are not <strong>NULL</strong>.</p><p>The result?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/487/1*RTHA8NWoC6H9wLhBh2x8mw.png" /></figure><p>As you already thought, it is 8 seats that have a ticket associated with them, so <strong>COUNT(ticket_id)</strong> returns 8.</p><blockquote>Did it matter that we have <strong>NULLs </strong>in our columns?</blockquote><p>Of course not! And that’s because <strong>COUNT(column_name)</strong> it counts every not null values in the column that you specified.</p><h3>Take away</h3><p>So, let’s have a short recap of what we have learned for our little Spider-Man movie night️🕷️</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5pqHrkwEga3GCA6V8E_4bw.png" /></figure><p>Remember: SQL doesn’t know that you’re counting cinema seats or booked tickets. It only goes after what you’ve asked it to count.</p><p>Now I’m sure that the next time you see <strong>COUNT(*)</strong> or <strong>COUNT(column_name)</strong>you won&#39;t have to wonder what you&#39;re actually counting. 😉</p><p>Below is the script with the data I used for the examples above:</p><pre>CREATE TABLE cinema_hall_1_seats (<br>    seat_id INT PRIMARY KEY,<br>    seat_number VARCHAR(5),<br>    ticket_id VARCHAR(10)<br>);<br><br>INSERT INTO cinema_hall_1_seats<br>    (seat_id, seat_number, ticket_id)<br>VALUES<br>    (1,  &#39;A1&#39;, &#39;T001&#39;),<br>    (2,  &#39;A2&#39;, &#39;T002&#39;),<br>    (3,  &#39;A3&#39;, NULL),<br>    (4,  &#39;A4&#39;, &#39;T003&#39;),<br>    (5,  &#39;A5&#39;, NULL),<br>    (6,  &#39;B1&#39;, &#39;T004&#39;),<br>    (7,  &#39;B2&#39;, NULL),<br>    (8,  &#39;B3&#39;, &#39;T005&#39;),<br>    (9,  &#39;B4&#39;, NULL),<br>    (10, &#39;B5&#39;, NULL),<br>    (11, &#39;C1&#39;, &#39;T006&#39;),<br>    (12, &#39;C2&#39;, &#39;T007&#39;),<br>    (13, &#39;C3&#39;, NULL),<br>    (14, &#39;C4&#39;, NULL),<br>    (15, &#39;C5&#39;, &#39;T008&#39;);</pre><p>P.S: I used Microsoft SQL Server Management Studio as my IDE 😄</p><p>So…Until next time, happy querying! 🧑 💻💓</p><p>🍿 Our data journey doesn’t end today,<br>There’s always more to learn along the way!</p><p>Explore more data stories on <a href="https://medium.com/@luchianadumitrescu"><strong>Medium</strong></a> and see what you might find,<br>And if you enjoy my articles, <a href="http://ko-fi.com/luchianadumitrescu"><strong>buy me a coffee</strong></a> — that’s incredibly kind! ☕</p><p>Thanks for stopping by and reading along,<br>Until next time, data friends — keep curiosity by your side! 💛</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2f4d99547f03" width="1" height="1" alt=""><hr><p><a href="https://code.likeagirl.io/count-vs-count-column-what-are-you-actually-counting-2f4d99547f03">COUNT(*) vs COUNT(column): What Are You Actually Counting?</a> was originally published in <a href="https://code.likeagirl.io/">Code Like A Girl</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Table-Valued Functions in SQL: Turning Requests Into Data Tables]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://code.likeagirl.io/table-valued-functions-in-sql-turning-requests-into-data-tables-f3e23d85cdc2?source=rss-92421d69473e------2"><img src="https://cdn-images-1.medium.com/max/2600/0*7iXlQt_lO5QTnrJI" width="6774"></a></p><p class="medium-feed-snippet">I&#x2019;m pretty sure all of us know how going out for dinner works. And no, I&#x2019;m not talking about all the preparations before leaving the house&#x2026;</p><p class="medium-feed-link"><a href="https://code.likeagirl.io/table-valued-functions-in-sql-turning-requests-into-data-tables-f3e23d85cdc2?source=rss-92421d69473e------2">Continue reading on Code Like A Girl »</a></p></div>]]></description>
            <link>https://code.likeagirl.io/table-valued-functions-in-sql-turning-requests-into-data-tables-f3e23d85cdc2?source=rss-92421d69473e------2</link>
            <guid isPermaLink="false">https://medium.com/p/f3e23d85cdc2</guid>
            <category><![CDATA[sql]]></category>
            <category><![CDATA[table-valued-function]]></category>
            <category><![CDATA[cross-apply]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[learning-with-analogies]]></category>
            <dc:creator><![CDATA[Luchiana Dumitrescu]]></dc:creator>
            <pubDate>Thu, 13 Aug 2026 09:36:01 GMT</pubDate>
            <atom:updated>2026-10-05T06:24:24.087Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[SQL Cross Apply — When SQL Thinks Like a Recommendation Engine]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://code.likeagirl.io/sql-cross-apply-when-sql-thinks-like-a-recommendation-engine-30961470f630?source=rss-92421d69473e------2"><img src="https://cdn-images-1.medium.com/max/2600/0*6ww19PFiuh6GEJjg" width="5760"></a></p><p class="medium-feed-snippet">Ah, online shopping is a blessing for us and a nightmare for our bank accounts (which is also ours, but the temptation is stronger&#x1F643;)</p><p class="medium-feed-link"><a href="https://code.likeagirl.io/sql-cross-apply-when-sql-thinks-like-a-recommendation-engine-30961470f630?source=rss-92421d69473e------2">Continue reading on Code Like A Girl »</a></p></div>]]></description>
            <link>https://code.likeagirl.io/sql-cross-apply-when-sql-thinks-like-a-recommendation-engine-30961470f630?source=rss-92421d69473e------2</link>
            <guid isPermaLink="false">https://medium.com/p/30961470f630</guid>
            <category><![CDATA[data-analytics]]></category>
            <category><![CDATA[data-engineering]]></category>
            <category><![CDATA[sql]]></category>
            <category><![CDATA[cross-apply]]></category>
            <category><![CDATA[learning-with-analogies]]></category>
            <dc:creator><![CDATA[Luchiana Dumitrescu]]></dc:creator>
            <pubDate>Thu, 09 Jul 2026 18:09:03 GMT</pubDate>
            <atom:updated>2026-07-10T06:28:20.062Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Can parenting chaos explain SQL Anti-Joins? I say: Of course]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://code.likeagirl.io/can-parenting-chaos-explain-sql-anti-joins-i-say-of-course-8f1c0f3cdea6?source=rss-92421d69473e------2"><img src="https://cdn-images-1.medium.com/max/2600/0*5GbsN9jA_0-kTohN" width="6720"></a></p><p class="medium-feed-snippet">Being a parent is both a pure blessing and, sometimes, a complete nightmare &#x2014; especially when you take your little one to the store.</p><p class="medium-feed-link"><a href="https://code.likeagirl.io/can-parenting-chaos-explain-sql-anti-joins-i-say-of-course-8f1c0f3cdea6?source=rss-92421d69473e------2">Continue reading on Code Like A Girl »</a></p></div>]]></description>
            <link>https://code.likeagirl.io/can-parenting-chaos-explain-sql-anti-joins-i-say-of-course-8f1c0f3cdea6?source=rss-92421d69473e------2</link>
            <guid isPermaLink="false">https://medium.com/p/8f1c0f3cdea6</guid>
            <category><![CDATA[data-analytics]]></category>
            <category><![CDATA[learn-sql]]></category>
            <category><![CDATA[learning-with-analogies]]></category>
            <category><![CDATA[anti-join]]></category>
            <category><![CDATA[sql]]></category>
            <dc:creator><![CDATA[Luchiana Dumitrescu]]></dc:creator>
            <pubDate>Mon, 01 Jun 2026 12:46:00 GMT</pubDate>
            <atom:updated>2026-06-01T18:32:31.423Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Game Night Matching and SQL SELF JOIN? Can it be that simple?]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@luchianadumitrescu/game-night-matching-and-sql-self-join-can-it-be-that-simple-9a70bf7827b6?source=rss-92421d69473e------2"><img src="https://cdn-images-1.medium.com/max/1536/1*r2H370VwE3cVaYdVnw352A.png" width="1536"></a></p><p class="medium-feed-snippet">A beginner-friendly guide to understanding SELF JOIN by matching people, not just data</p><p class="medium-feed-link"><a href="https://medium.com/@luchianadumitrescu/game-night-matching-and-sql-self-join-can-it-be-that-simple-9a70bf7827b6?source=rss-92421d69473e------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@luchianadumitrescu/game-night-matching-and-sql-self-join-can-it-be-that-simple-9a70bf7827b6?source=rss-92421d69473e------2</link>
            <guid isPermaLink="false">https://medium.com/p/9a70bf7827b6</guid>
            <category><![CDATA[data-engineering]]></category>
            <category><![CDATA[sql]]></category>
            <category><![CDATA[join]]></category>
            <category><![CDATA[data-analytics]]></category>
            <category><![CDATA[learning-with-analogies]]></category>
            <dc:creator><![CDATA[Luchiana Dumitrescu]]></dc:creator>
            <pubDate>Sat, 09 May 2026 17:57:51 GMT</pubDate>
            <atom:updated>2026-05-09T17:58:50.714Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[INNER JOIN vs LEFT JOIN in SQL: What’s the difference?]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://code.likeagirl.io/inner-join-vs-left-join-in-sql-whats-the-difference-c72ade418649?source=rss-92421d69473e------2"><img src="https://cdn-images-1.medium.com/max/2600/0*0vX61q8fxDphcnLc" width="6000"></a></p><p class="medium-feed-snippet">Struggling to understand SQL JOINs? Learn the difference between INNER JOIN and LEFT JOIN through a simple (and fun) dating app analogy</p><p class="medium-feed-link"><a href="https://code.likeagirl.io/inner-join-vs-left-join-in-sql-whats-the-difference-c72ade418649?source=rss-92421d69473e------2">Continue reading on Code Like A Girl »</a></p></div>]]></description>
            <link>https://code.likeagirl.io/inner-join-vs-left-join-in-sql-whats-the-difference-c72ade418649?source=rss-92421d69473e------2</link>
            <guid isPermaLink="false">https://medium.com/p/c72ade418649</guid>
            <category><![CDATA[sql-inner-join]]></category>
            <category><![CDATA[sql-left-join]]></category>
            <category><![CDATA[sql]]></category>
            <category><![CDATA[learning-with-analogies]]></category>
            <category><![CDATA[data-engineering]]></category>
            <dc:creator><![CDATA[Luchiana Dumitrescu]]></dc:creator>
            <pubDate>Mon, 13 Apr 2026 11:16:01 GMT</pubDate>
            <atom:updated>2026-04-13T17:58:52.884Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[I Found 9+ Date Formats in One Column… Here’s How I Tamed Them with SQL]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://code.likeagirl.io/i-found-9-date-formats-in-one-column-heres-how-i-tamed-them-with-sql-2e99b8ed3528?source=rss-92421d69473e------2"><img src="https://cdn-images-1.medium.com/max/2600/0*IFKisLwPtSkvLjen" width="2992"></a></p><p class="medium-feed-snippet">A practical, real-world approach to detecting, cleaning, and standardizing messy date formats using SQL</p><p class="medium-feed-link"><a href="https://code.likeagirl.io/i-found-9-date-formats-in-one-column-heres-how-i-tamed-them-with-sql-2e99b8ed3528?source=rss-92421d69473e------2">Continue reading on Code Like A Girl »</a></p></div>]]></description>
            <link>https://code.likeagirl.io/i-found-9-date-formats-in-one-column-heres-how-i-tamed-them-with-sql-2e99b8ed3528?source=rss-92421d69473e------2</link>
            <guid isPermaLink="false">https://medium.com/p/2e99b8ed3528</guid>
            <category><![CDATA[data-quality]]></category>
            <category><![CDATA[standardization]]></category>
            <category><![CDATA[sql]]></category>
            <category><![CDATA[learning-with-analogies]]></category>
            <category><![CDATA[data-cleaning]]></category>
            <dc:creator><![CDATA[Luchiana Dumitrescu]]></dc:creator>
            <pubDate>Tue, 31 Mar 2026 18:33:29 GMT</pubDate>
            <atom:updated>2026-04-02T21:20:22.980Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[I found at least 9 different date formats in one SQL column — Here’s how i detected them]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://code.likeagirl.io/i-found-at-least-9-different-date-formats-in-one-sql-column-heres-how-i-detected-them-635a49786c35?source=rss-92421d69473e------2"><img src="https://cdn-images-1.medium.com/max/2600/0*-DpSH6ztiEL2G96Y" width="3999"></a></p><p class="medium-feed-snippet">A simple SQL pattern-detection query that helped uncover messy date formats hidden inside a legacy database.</p><p class="medium-feed-link"><a href="https://code.likeagirl.io/i-found-at-least-9-different-date-formats-in-one-sql-column-heres-how-i-detected-them-635a49786c35?source=rss-92421d69473e------2">Continue reading on Code Like A Girl »</a></p></div>]]></description>
            <link>https://code.likeagirl.io/i-found-at-least-9-different-date-formats-in-one-sql-column-heres-how-i-detected-them-635a49786c35?source=rss-92421d69473e------2</link>
            <guid isPermaLink="false">https://medium.com/p/635a49786c35</guid>
            <category><![CDATA[sql]]></category>
            <category><![CDATA[data-standardization]]></category>
            <category><![CDATA[data-engineering]]></category>
            <category><![CDATA[data-cleaning]]></category>
            <category><![CDATA[learning-with-analogies]]></category>
            <dc:creator><![CDATA[Luchiana Dumitrescu]]></dc:creator>
            <pubDate>Wed, 11 Mar 2026 14:49:40 GMT</pubDate>
            <atom:updated>2026-03-11T15:14:52.934Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Is your SQL speaking a different language?]]></title>
            <link>https://code.likeagirl.io/is-your-sql-speaking-a-different-language-0238b380dbb1?source=rss-92421d69473e------2</link>
            <guid isPermaLink="false">https://medium.com/p/0238b380dbb1</guid>
            <category><![CDATA[sql-date-format]]></category>
            <category><![CDATA[data-standardization]]></category>
            <category><![CDATA[data-quality]]></category>
            <category><![CDATA[learning-with-analogies]]></category>
            <category><![CDATA[sql]]></category>
            <dc:creator><![CDATA[Luchiana Dumitrescu]]></dc:creator>
            <pubDate>Wed, 04 Feb 2026 15:07:57 GMT</pubDate>
            <atom:updated>2026-02-04T15:07:57.200Z</atom:updated>
            <content:encoded><![CDATA[<h3>Are Your SQL Dates Speaking a Different Language?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*gY5nFrqLX7ERaze1" /><figcaption>Photo by <a href="https://unsplash.com/@brett_jordan?utm_source=medium&amp;utm_medium=referral">Brett Jordan</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>I think some of us have experienced a situation like this: you’re approached by someone who doesn’t speak the local language and only knows a bit of English. There’s no translator app, no shared vocabulary, but just a few common words and a lot of gestures (and yes, your arms might feel like they’re about to fall off 😂).</p><blockquote>“So how do colleagues in international teams handle this?”</blockquote><p>The answer is simple: they often rely on English, and not because it’s anyone’s native tongue, but because it allows everyone to understand each other.</p><blockquote>The same thing applies to date formats in SQL.</blockquote><blockquote>Feeling a bit lost? Don’t worry — you’ll get it in no time once we move to the next section, just stay with me 😄</blockquote><h3>Are different date formats like different dialects?</h3><p>Each user, system, or country has its own “native” way of writing dates, and locally, those formats feel perfectly natural; It’s like everyone is trying to speak English, but each in their own dialect.</p><p>But the moment data is shared, joined, filtered, or reported across systems, those differences turn into misunderstandings.</p><p>So without a common language for dates, SQL doesn’t fail loudly, but it returns results that look correct but quietly mean something else.</p><h3>When life problems hit</h3><p>I think it’s time to let the cat out of the bag of one of my recent projects (not recommended 😅).</p><p>One of the clients had an old application and a database, and recently, it wanted to go to the cloud (on cloud nine maybe 😂). The application was something like “my precious” for him, and I had to be very careful.</p><p>As a BI Developer, as soon as I received access to the data, I started to get my hands dirty (oh yeah 😎). But soon my enthusiasm hit rock bottom when I tried to see the data format they are using.</p><h4>The result? Total disaster 😭</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/835/1*2QLD6pSHDQebBgJy_p-4xQ.png" /></figure><p>It started to look like a horror movie with no door to escape, like a maze with no exit, and like a problem with no solution; and somehow I was like the guy in the gif below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/498/1*W1093o6QCf-Uescsg3tPZA.gif" /><figcaption>Lord, have mercy!</figcaption></figure><p>The first thing that popped into my mind was “How on Earth is this thing possible??”…and the answer didn’t take long to come…the app let the user&#39;s imagination run wild with free-text fields (<strong>BIG NO, NEVER WHEN IT COMES TO DATES</strong>).</p><h3>What is this data standardization?</h3><p>To keep things simple and restore some zen, <strong>data standardization means defining a common set of rules that everyone follows when storing data, </strong>whether they like it or not 😂.</p><p>These are not some things that were made to be violated, because it keeps things predictable and consistent, so the database doesn’t turn into a guessing game every time you run a query.</p><p><strong>— OR, my special version —</strong></p><p>Data standardization is like a common rule that everyone SHOULD obey (not too zen, right? 😂)</p><p>We’ll talk about how to deal with all of this in a future article, so don’t worry — I won’t leave you lost in the fog.</p><h3>Why does it hurt so much?</h3><p>When your users have so much freedom with a free-text field and freedom of choice, the database becomes a linguistic experiment. Dates show up in every format imaginable — regional standards, personal preferences, copy-pasted emails, and occasionally something that looks more like a suggestion than a date</p><blockquote>Please, someone remind those people that SQL isn’t a mind reader! You can’t expect it to understand intent, context, or “what I meant” without hesitation, effort, or complaints🙏🙏</blockquote><p><strong>So why does it hurt?</strong> Well, aside from the fact that your eyes, as a data fellow, are one bad query away from taking a long vacation after witnessing that nuclear attack, your entire pipeline starts to suffer. Suddenly, everything requires extra transformations, validations, and edge-case handling, and there’s no way you’ll be able to deliver that cutie-pie dashboard everyone expects.</p><p><strong>And why?</strong> Because nothing actually breaks. Queries still run. Reports still load. Filters still return results. But those results may be quietly wrong. A date interpreted as 03/04/2024 might mean April 3rd for one system and March 4th for another—and <strong>SQL </strong>won’t warn you about it. It will confidently give you an answer, just not the one you thought you were asking for.</p><h3>Why so many consequences?</h3><p>When there are no rules, Brownian motion feels right at home. Dates move in every direction, formats collide, and <strong>SQL </strong>is left trying to make sense of noise that looks like data.</p><p>Below is the list of possible disasters:</p><ol><li><strong>Wrong results that look right — </strong>the most dangerous one, because SQL will happily run your query and return results that <em>look</em> perfectly valid. But it’s just a trap because 01/02/2024 might mean January 2nd or February 1st, which is not what is desired.</li><li><strong>Filtering and grouping are silently sabotaged — </strong>When dates are stored in inconsistent formats, or even worse, as strings, comparisons like:</li></ol><ul><li>“last 30 days”</li><li>“current month”</li><li>“before 2023–12–31”</li></ul><p>become unreliable or even incorrect.</p><p>3. <strong>The transformations are complex, but fragile —</strong> you’ll end with a lot of CAST, CONVERT, or PARSE calls. The result? Heavier processing, slower queries, harder maintenance, and higher costs, and that’s all because the data wasn’t standardized at the source.</p><p>4. <strong>A looot of inconsistencies — </strong>based on how the dates were guessed by SQL, the reports answering the same question may proudly display different results.<br> No one feels responsible, and suddenly dashboards are described as “indicative” instead of “reliable.”</p><p>5. I<strong>ntegrations with other systems? —</strong> better get rid of the idea, because it will be a nightmare when the assumptions collide, and the implied systems have different defaults, parsing rules, and formats.</p><p>6. <strong>The bill arrives when you least expect it — i</strong>nconsistent date formats in historical data always resurface. And when they do, you’re forced to clean them up retroactively, an exercise that is significantly more expensive, risky, and time-consuming than doing it right from the start.</p><p>The last one almost destroyed my nerves. Days of frustration, endless discussions with the business to confirm whether standardization was <em>really</em> necessary, and multiple failed attempts at damage control.<br> But once the problem was finally solved, I could breathe again — and the data did too.</p><h3>Take away</h3><p>Data standardization isn’t about being strict or taking away freedom; it’s about making sure everyone speaks the same language. Just like international teams rely on English to avoid misunderstandings, databases rely on standardized formats to keep data predictable and meaningful.</p><p>Dates, in particular, may look harmless, but without clear rules they quickly become a source of silent errors, fragile pipelines, and endless frustration.</p><p>Everyone wants a reliable and robust data model, but it’s easy to forget that SQL is not a fortune teller trying to guess what humans <em>meant</em>. And in the end, data — just like people — works best when everyone understands each other.</p><p><em>Stay tuned and also, do not forget you can find other interesting data-related articles on my </em><a href="https://medium.com/@luchianadumitrescu"><strong><em>Medium</em></strong></a><strong><em>.</em></strong></p><p><em>If you like my articles, let’s spend our coffee break together</em><strong><em> </em></strong><a href="http://ko-fi.com/luchianadumitrescu"><strong><em>here</em></strong></a><strong><em>. </em></strong><em>Thank you for your support!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0238b380dbb1" width="1" height="1" alt=""><hr><p><a href="https://code.likeagirl.io/is-your-sql-speaking-a-different-language-0238b380dbb1">Is your SQL speaking a different language?</a> was originally published in <a href="https://code.likeagirl.io/">Code Like A Girl</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From Stars to Snowflakes: Understanding Database Schemas the Winter Way]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://code.likeagirl.io/from-stars-to-snowflakes-understanding-database-schemas-the-winter-way-9aba79b603d1?source=rss-92421d69473e------2"><img src="https://cdn-images-1.medium.com/max/2600/0*yvjRVTmVj4H9asoa" width="4032"></a></p><p class="medium-feed-snippet">If you&#x2019;re not a Medium member, you can still enjoy the full article for free. Click HERE to read it all&#x1F60A;</p><p class="medium-feed-link"><a href="https://code.likeagirl.io/from-stars-to-snowflakes-understanding-database-schemas-the-winter-way-9aba79b603d1?source=rss-92421d69473e------2">Continue reading on Code Like A Girl »</a></p></div>]]></description>
            <link>https://code.likeagirl.io/from-stars-to-snowflakes-understanding-database-schemas-the-winter-way-9aba79b603d1?source=rss-92421d69473e------2</link>
            <guid isPermaLink="false">https://medium.com/p/9aba79b603d1</guid>
            <category><![CDATA[learning-with-analogies]]></category>
            <category><![CDATA[data-modeling]]></category>
            <category><![CDATA[editors-pick]]></category>
            <category><![CDATA[data-warehouse]]></category>
            <category><![CDATA[sql]]></category>
            <dc:creator><![CDATA[Luchiana Dumitrescu]]></dc:creator>
            <pubDate>Mon, 08 Dec 2025 05:58:12 GMT</pubDate>
            <atom:updated>2025-12-08T14:19:05.599Z</atom:updated>
        </item>
    </channel>
</rss>