| From: | Mario de Frutos Dieguez <mariodefrutos(at)gmail(dot)com> |
|---|---|
| To: | |
| Cc: | pgsql-admin(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Problem with a "complex" upsert |
| Date: | 2018-06-21 14:46:12 |
| Message-ID: | CADc-R5jOpS8zH9M6LzRTowU_f2_1VsjdO82EoJHmS98yxQwTHQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-bugs |
In this case is just one column but in other queries I'm updating
multiple columns thats why I set the ROW thing
2018-06-21 16:40 GMT+02:00 Geoff Winkless <pgsqladmin(at)geoff(dot)dj>:
> On Thu, 21 Jun 2018 at 15:07, Mario De Frutos Dieguez
> <mariodefrutos(at)gmail(dot)com> wrote:
>>
>> ON CONFLICT (geoid) DO UPDATE SET (b01003001) = ROW(EXCLUDED.b01003001);
>
> At first glance, shouldn't the query simply be
>
> SET b01003001 = EXCLUDED.b01003001;
>
> ?
>
> The second part of your email does suggest a bug though, syntax shouldn't
> cause a crash.
>
> Geoff
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Geoff Winkless | 2018-06-21 16:48:39 | Re: Problem with a "complex" upsert |
| Previous Message | Geoff Winkless | 2018-06-21 14:40:51 | Re: Problem with a "complex" upsert |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sara Pranke | 2018-06-21 15:05:01 | Re: BUG #15250: ERROR: could not find pathkey item to sort |
| Previous Message | Geoff Winkless | 2018-06-21 14:40:51 | Re: Problem with a "complex" upsert |