Views of aggregate without GROUP BY clause always have
only one tuple as the result. Even when all tuples in base
tables are deleted, the view must have a row whose result is
0 for count(), or NULL for others.
However, in the previous implementation, this resulted in
deleting the tuple from the view. To fix this, don't allow
to delete a tuple from a view when this is a aggregate view
without GROUP BY.
Views of aggregate without GROUP BY clause always have only one tuple as the result. Even when all tuples in base tables are deleted, the view must have a row whose result is 0 for count(), or NULL for others.
However, in the previous implementation, this resulted in deleting the tuple from the view. To fix this, don't allow to delete a tuple from a view when this is a aggregate view without GROUP BY.
Github issue #88