SQL FROM
Tells the database which table to read from — every query needs one.
What & Why
FROM names the table a query reads its rows from. It always follows SELECT in how you write a query, though the database actually reads FROM first when it runs — a detail covered in the Execution Order lesson.
See How It Works
| 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 |
EXAMPLE QUERY
SELECT name
FROM marketing.campaigns;RESULT
| name |
|---|
| Spring Launch |
| Retention Webinar |
| Finance Retargeting |
| Enterprise Search |
The result uses the same Queryflo columns shown in the worked example.
Now You Try
Practice this concept
Product needs the first ten feature names and their owning teams. Read the data from the real product feature table.
Available schema
productPrefix tables with product.table_name.
nameteamproduct.features| Column | Type |
|---|---|
| id | integer |
| name | text |
| description | text |
| team | text |
| released_at | timestamp with time zone |
| deprecated_at | timestamp with time zone |
| internal_priority | integer |
query.sql
Sign up free to try it on a real business scenario