A query describes the rows and columns a reader needs. Start with named columns instead of SELECT * when you publish a report. Extra columns can expose details that the report never requested, and a later schema change can alter the result.
The orders table has one row per order. Customers have their own IDs, and one customer can place several orders. Keep that distinction when you describe what a row means. Column aliases give calculated fields a useful label without changing their values.
This workspace runs PostgreSQL through PGlite in your browser. Run a query to inspect its result, then check it against the task. The displayed data is fictional.
The hidden copy changes records so your query must express a rule.
Return the order ID, status and amount in the requested order.