You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since count(*) is parsed to COUNTALL in the SQL and MyriaL parsers, COUNTALL should be translated to count(*) in SQL generation. The intended semantics are exactly the same (count all tuples regardless of NULL values). Even though we don't support NULL in raco or Myria, it's possible that count(*) can be more effectively optimized in Postgres than count($0), and the semantics will be correct if/when we do decide to support NULL.
The text was updated successfully, but these errors were encountered:
Since
count(*)
is parsed toCOUNTALL
in the SQL and MyriaL parsers,COUNTALL
should be translated tocount(*)
in SQL generation. The intended semantics are exactly the same (count all tuples regardless of NULL values). Even though we don't support NULL in raco or Myria, it's possible thatcount(*)
can be more effectively optimized in Postgres thancount($0)
, and the semantics will be correct if/when we do decide to support NULL.The text was updated successfully, but these errors were encountered: