Comments and Statements
Part of the First Queries section of Coddy's PostgreSQL journey. Lesson 3 of 20.
A comment explains a query without becoming part of its result. PostgreSQL ignores text from -- to the end of a line. A semicolon ends a statement, so a script can contain more than one statement.
Input table products:
id | name | category | price | stock | active | note |
|---|---|---|---|---|---|---|
1 | Map | travel | 12 | 5 | True | NULL |
2 | Notebook | books | 8 | 0 | True | Recycled |
3 | Atlas | books | 24 | 3 | False | NULL |
4 | Mug | home | 12 | 8 | True | Blue |
5 | lamp | home | 30 | 2 | False | Clearance |
6 | Mini map | travel | 6 | 10 | True | NULL |
-- Read the catalog
SELECT category FROM products;The comment is skipped and the query returns categories. In this editor, when several statements run, the final statement supplies the result table. Keep the query you want checked last.
Use -- for a line comment. End each statement with ; and leave the required result query last.
Challenge
EasyWrite a line comment describing a stock check, then return name and price for all products. Row order does not matter.
The input tables are shown in the test panel. Each run starts from fresh data. Return the named columns in the stated order; do not hard-code the displayed rows.
Try it yourself
-- Write your SQL here.
This lesson includes a short quiz. Start the lesson to answer it and track your progress.
All lessons in First Queries
Practice on your own: PostgreSQL playground