In the context of aliases, which clause allows using a calculated value?

The clause that allows the use of a calculated value is the HAVING clause. The HAVING clause is specifically designed to filter records after aggregate functions have been applied, making it suitable for conditions that test calculated results from the data, such as sums, averages, counts, etc.

In contrast, the WHERE clause cannot utilize calculated values derived from the SELECT statement, such as created column aliases or results of aggregate functions. The WHERE clause is executed before any calculations are performed, thus restricting it to basic conditions that do not involve aggregate calculations.

The SELECT clause is used for selecting and renaming columns and can incorporate calculations, but it does not filter records based on those calculations. Similarly, the ORDER BY clause can sort the result set based on calculated fields but does not filter or impose conditions on the data.

In summary, when it comes to utilizing calculated values in filtering, the HAVING clause stands out as the appropriate choice, particularly when those values are derived from aggregate functions or are column aliases from the SELECT statement.