N009-E3 Tier 1 · Foundations · easy

Return the total hours in a single column named `hours_worked`. The `AS` keyword is optional — `9 * 8 hours_worked` works the same as `9 * 8 AS hours_worked`

Part of Column Aliases and Expression Naming in SQL

The problem

A timesheet analyst is calculating billable hours for a contractor engagement. The contractor worked 9 days at 8 hours per day.

Write a query to return the total hours in a single column named hours_worked. The AS keyword is optional — 9 * 8 hours_worked works the same as 9 * 8 AS hours_worked.

Output:

  • A single row with one column named hours_worked, containing the total.

Run previews · Check grades

Write a query, then run it to see results here.

Worked solution Try it yourself first
Solution query
SELECT
  9 * 8 hours_worked

The shape

The identifier sitting right after the multiplication is the alias, even with no AS keyword between them. PostgreSQL treats a bare identifier following an expression in the SELECT list as the column name for that expression.

Clause by clause

  • SELECT 9 * 8 hours_worked evaluates the multiplication and labels the result. 9 * 8 returns 72, and hours_worked becomes the column header. There's no FROM because the day count and the daily hours come straight from the prompt as integer literals.
  • The whitespace between 8 and hours_worked is what tells PostgreSQL the identifier is an alias and not part of the arithmetic. There's no operator that could join an integer to an identifier, so the parser reads the identifier as the optional alias position.

Why this and not 9 * 8 AS hours_worked

Both return the same row with the same column header. The AS keyword is optional in PostgreSQL's grammar; the alias position exists with or without it. The shorter form saves one word, and it shows up in older codebases and in code from analysts who learned SQL on a dialect where AS was less emphasised.

The longer form is clearer. With AS written out, the alias is unmistakable. Without it, a scan of SELECT 9 * 8 hours_worked can read for a half-second like there's a missing operator before the identifier. Writing AS is the safer habit; recognising the form without it is the skill that lets you read other people's code.

You practiced aliasing a column with the AS keyword omitted. PostgreSQL accepts expression alias_name as shorthand for expression AS alias_name — useful to recognise in legacy code, though writing AS explicitly is clearer.

How you actually get good at SQL

Reading explains SQL. Writing it, over and over with instant feedback, is what makes you fluent.

That's the whole SQLMaxx loop: 600+ real problems, instant AI feedback, mastery you can actually see, and spaced review that won't let you forget.

A stack of SQL practice problem cards, the top card showing an employees table.
615 problems · 66 concepts

Real problems. Not toy examples.

615 hand-built problems spanning all 66 concepts, from basic SELECTs to window functions, built on real schemas and real business questions, the kind you'll actually get asked on the job. Enough reps to make SQL automatic.

A retro computer showing a SQL query marked correct with a green checkmark.
Instant AI feedback

Write a query. Know if it's right in one second.

No copying an answer and hoping it clicked. The AI grader checks your real query against real data, catches exactly what's wrong, and explains the fix in plain English, like a senior analyst reading over your shoulder on every problem.

A circular mastery progress dial filling from blue to green, the SQLMaxx diamond at its center.
Mastery tracking

Stop guessing whether you actually know it.

SQLMaxx tracks every concept and shows you what you've mastered and what's still shaky. Your skills fill in one concept at a time, so 'I think I get joins' becomes something you can prove.

A SQL query editor circled by a blue return arrow with a clock, scheduled to come back for review.
Spaced review

Learn it once. Keep it for good.

Most of what you learn this week fades by next week. So when a concept comes due for review, SQLMaxx hands you a fresh problem to solve from a blank editor, not a flashcard to re-read. A research-backed spaced-repetition algorithm (FSRS) times each return for right before you'd forget, so your SQL is still there months later, when the interview or the job actually needs it.

Practice, feedback, mastery, review. That's the loop that turns reading into real skill.

Start free

No account, no credit card. Start solving in under a minute.