In a query using both WHERE and HAVING, which statement about the order of processing is correct?
Dans une requête qui utilise à la fois WHERE et HAVING, quelle affirmation sur l'ordre de traitement est correcte ?
Answers
AWHERE filters rows before grouping; HAVING filters groups after aggregationWHERE filtre les lignes avant le regroupement ; HAVING filtre les groupes après l'agrégation
BHAVING runs first on individual rows, and WHERE runs afterwards on the finished groupsHAVING s'exécute d'abord sur les lignes, puis WHERE sur les groupes terminés
CWHERE and HAVING are identical and can always be swappedWHERE et HAVING sont identiques et toujours interchangeables
DHAVING can only be used without GROUP BYHAVING ne peut s'utiliser que sans GROUP BY
The answer and explanation are in the full bank.
This question is one of 2,831 in the paid banks. Each comes with the correct answer and the reasoning behind it, not just a mark.
Unlock for 5,000 RWFMIFOTRA exam practicealigned to Practice set: Database Management·3 marks·Hard
More Database questions
- What is the main role of a database management system (DBMS) such as PostgreSQL, MySQL or SQL Server?
- In a relational table called Applicants, what does a single row represent?
- Which two properties must every primary key value have?
- The Employees table has a DistrictID column that must always refer to an existing row in the Districts table. What enforces this rule?
- An ExamResults table records one score per candidate per paper. Neither CandidateID nor PaperID is unique on its own. What is a suitable primary key?
- A designer gives each applicant an auto-generated ApplicantID as the primary key, and stores the national ID number as a separate unique column. Why use this surrogate key?
- One district has many sectors, and each sector belongs to exactly one district. What type of relationship is this?
- Each trainee can attend many courses, and each course has many trainees. How is this relationship stored in a relational database?