From: | "Ravi Krishna" <srkrishna(at)myself(dot)com> |
---|---|
To: | |
Cc: | "Vikas Sharma" <shavikas(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: SQL query |
Date: | 2019-04-18 18:40:15 |
Message-ID: | trinity-ccf02f29-8fd9-417f-8b6d-f57a39426ebd-1555612815386@3c-app-mailcom-lxa14 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Oh wait. I see that it in both cases it did update correct target rows, but the value of col1 for non matching rows
is different. In the first case (and col2), the non matching rows also got updated.
So yes, same behavior like yours.
> Sent: Thursday, April 18, 2019 at 2:36 PM
> From: "Ravi Krishna" <srkrishna(at)myself(dot)com>
> To: "Vikas Sharma" <shavikas(at)gmail(dot)com>
> Cc: pgsql-general(at)lists(dot)postgresql(dot)org
> Subject: Re: SQL query
>
> Not able to produce this with PG 11.1
>
> If col1 is any type other than boolean, the update statement fails in syntax.
> If col1 is boolean, then it updated it correctly. In other words
> update col1 = NULL
> and col2 in (1,2)
> is treated same as
> update col1 = NULL
> where col2 in (1,2)
>
> Also I checked it on DB2 which rejected the UPDATE sql as bad syntax, as expected.
>
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2019-04-18 18:41:16 | Re: SQL query |
Previous Message | Ravi Krishna | 2019-04-18 18:36:35 | Re: SQL query |