---
title: "Discussion on \"Why a LEFT JOIN reports 100% activation when three users never activated\" | Hashnode"
description: "Discussion on \"Why a LEFT JOIN reports 100% activation when three users never activated\". Reproduce a PostgreSQL LEFT JOIN mistake, recover the users lost by WHERE, and verify the activation rate with data you can run."
url: "https://hashnode.com/posts/why-a-left-join-reports-100-activation-when-three-users-never-activated/6ad4d919e04956dc073b96a3"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Why a LEFT JOIN reports 100% activation when three users never activated](https://sqlbrief.hashnode.dev/why-a-left-join-reports-100-activation-when-three-users-never-activated?utm_source=hashnode&utm_medium=feed)

Reproduce a PostgreSQL LEFT JOIN mistake, recover the users lost by WHERE, and verify the activation rate with data you can run.

Oct 18 · 12 min read · sqlbrief.hashnode.dev  
Read the article

-   [#sql](https://hashnode.com/tag/sql)
-   [#postgresql](https://hashnode.com/tag/postgresql)
-   [#data-analytics](https://hashnode.com/tag/data-analytics)

## Written by

[Aleks](https://hashnode.com/@aleks-sqlbrief)

@aleks-sqlbrief

  
[View profile](https://hashnode.com/@aleks-sqlbrief)

Building SQLBrief: hands-on SQL practice, from your first query to product analytics.

I'm Aleks, building SQLBrief. I write about SQL mistakes that change the meaning of a report, with examples you can run yourself. SQLBrief offers browser-based SQL practice in English and Russian.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
