projects / postgresql.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: e256baf) | patch
Disallow aggregate functions in UPDATE commands (unless within a sub-SELECT).
authorTom Lane <tgl@sss.pgh.pa.us>
Wed, 21 Jun 2006 18:30:11 +0000 (18:30 +0000)
committerTom Lane <tgl@sss.pgh.pa.us>
Wed, 21 Jun 2006 18:30:11 +0000 (18:30 +0000)
commit1f5ca045a435bc6aa9c98d7296973925c5208add
tree0d72663e4a8fc19315b2a166ef0e6cc9369218cdtree
parente256bafaa2aec06dd9dc9493c4e600319ab11525commit | diff
Disallow aggregate functions in UPDATE commands (unless within a sub-SELECT).
This is disallowed by the SQL spec because it doesn't have any very sensible
interpretation.  Historically Postgres has allowed it but behaved strangely.
As of PG 8.1 a server crash is possible if the MIN/MAX index optimization gets
applied; rather than try to "fix" that, it seems best to just enforce the
spec restriction.  Per report from Josh Drake and Alvaro Herrera.
src/backend/parser/analyze.c diff | blob | blame | history
This is the main PostgreSQL git repository.