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
SQL group-by queries have a well-defined general semantics, but actually use strange heuristics to decide what can and cannot be grouped over. I'm not quite sure how to handle this. One possibility would be to use a syntactical test to forbid any kind of expressions other than field accesses in the by part, but this removes useful use-case with, indeed, integer computations. Maybe the Postgresql criterion could be emulated in a more fine-grained way, but that won't be portable at all.
A macaque query like:
is accepted but rejected by postgresql with the following error message:
ERROR: 42601: non-integer constant in GROUP BY
The text was updated successfully, but these errors were encountered: