SQL OR
A row survives if at least ONE condition is true — the opposite bar from AND.
What & Why
OR combines two or more conditions — a row survives if any of them is true, even if the rest are false.
See How It Works
BUSINESS QUESTION
Campaigns in email, or campaigns with spend greater than 55,000.
| id | name | channel | spend | start_date | end_date | status | target_segment |
|---|---|---|---|---|---|---|---|
| 1 | Spring Launch | google_ads | 55000.00 | 2024-01-15 | 2024-03-31 | active | smb |
| 2 | Retention Webinar | 45000.00 | 2024-02-10 | 2024-04-15 | active | enterprise | |
| 3 | Finance Retargeting | 50000.00 | 2024-03-12 | 2024-05-31 | active | enterprise | |
| 4 | Enterprise Search | google_ads | 60000.00 | 2024-04-01 | 2024-06-30 | active | enterprise |
Watch or check each rowRow 1 of 4
-- checking Spring Launch: google_ads = email OR 55000 > 55000?FALSE — dropped| name | channel | spend |
|---|---|---|
| Spring Launch | google_ads | 55000 |
| Retention Webinar | 45000 | |
| Finance Retargeting | 50000 | |
| Enterprise Search | google_ads | 60000 |
channel = 'email' OR spend > 55000 is false for Spring Launch.
EXAMPLE QUERY
SELECT name FROM marketing.campaigns
WHERE channel = 'email' OR spend > 55000;Now You Try
Practice this concept
Growth wants users who are either on the Pro plan or located in the US.
Available schema
growthPrefix tables with growth.table_name.
idcountryplangrowth.users| Column | Type |
|---|---|
| id | integer |
| created_at | timestamp with time zone |
| country | text |
| channel | text |
| plan | text |
| activated_at | timestamp with time zone |
| churned_at | timestamp with time zone |
| legacy_user_code | text |
query.sql
Sign up free to try it on a real business scenario