I have following query in PostgreSQL:
SELECT
COUNT(a.log_id) AS overall_count
FROM
"Log" as a,
"License" as b
WHERE
a.license_id=7
AND
a.license_id=b.license_id
AND
b.limit_call > overall_count
GROUP BY
a.license_id;
Why do I get this error:
ERROR: column "overall_count" does not exist
My table structure:
License(license_id, license_name, limit_call, create_date, expire_date)
Log(log_id, license_id, log, call_date)
I want to check if a license has reached the limit for calls in a specific month.
SELECT a.license_id, a.limit_call
, count(b.license_id) AS overall_count
FROM "License" a
LEFT JOIN "Log" b USING (license_id)
WHERE a.license_id = 7
GROUP BY a.license_id -- , a.limit_call -- add in old versions
HAVING a.limit_call > count(b.license_id)
Major points
In versions prior to PostgreSQL 9.1 you have to add
limit_callto theGROUP BYclause. Beginning with version 9.1 it is enough to have the primary key in theGROUP BYclause. The release notes for 9.1:Allow non-
GROUP BYcolumns in the query target list when the primary key is specified in theGROUP BYclauseYour
WHEREcondition has to move to theHAVINGclause since it refers to the result of an aggregate function. And you cannot refer to output columns (column aliases) in theHAVINGclause, where you can only reference input columns. So you have to repeat the expression. Per documentation:An output column's name can be used to refer to the column's value in
ORDER BYandGROUP BYclauses, but not in theWHEREorHAVINGclauses; there you must write out the expression instead.I reversed the order of tables in the
FROMclause and cleaned up the syntax a bit to make it less confusing.USINGis just a notational convenience here.I used
LEFT JOINinstead ofJOIN, so you do not exclude licenses without any logs at all.I would advise not to use mixed case identifiers in Postgres if possible. Very error prone.
Only non-null values are counted by
count(). Since you want to count related entries in table"Log"it is safer and slightly cheaper to usecount(b.license_id). This column is used in the join, so we don't have to bother whether the column can be null or not.count(*)is even shorter and slightly faster, yet. If you don't mind to get a count of1for0rows in the left table, use that.
The where query doesn't recognize your column alias, and furthermore, you're trying to filter out rows after aggregation. Try:
SELECT
COUNT(a.log_id) AS overall_count
FROM
"Log" as a,
"License" as b
WHERE
a.license_id=7
AND
a.license_id=b.license_id
GROUP BY
a.license_id
having b.limit_call > count(a.log_id);
The having clause is similar to the where clause, except that it deals with columns after an aggregation, whereas the where clause works on columns before an aggregation.
Also, is there a reason why your table names are enclosed in double quotes?
来源:https://stackoverflow.com/questions/8119489/postgresql-where-count-condition