On Thu, Jun 20, 2019 at 2:13 PM Harry Ambrose <harry.ambr...@gmail.com> wrote:
> Hi, > > I noticed some weird update behaviour today in one of our development > environments. In my opinion this appears to be a bug, but before reporting > it I thought I should seek the opinions of others in the community. Maybe > this is known and/or seen before? > Yep, seen before, even has an FAQ entry: https://wiki.postgresql.org/wiki/FAQ#Why_doesn.27t_PostgreSQL_report_a_column_not_found_error_when_using_the_wrong_name_in_a_subquery.3F > The behaviour is visible when a subquery is used in an update. More > specifically when a subquery is rejected by the parser when executed on > it's own. This causes the where condition to be ignored entirely and thus > the whole table updated rather than the parser throwing an error. > David J.
