| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | "drum(dot)lucas(at)gmail(dot)com" <drum(dot)lucas(at)gmail(dot)com> |
| Cc: | Charles Clavadetscher <clavadetscher(at)swisspug(dot)org>, Postgres General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Update field to a column from another table |
| Date: | 2016-04-21 19:11:13 |
| Message-ID: | CAKFQuwZVDHV_ub+BEe+EUaMXLisD3_CdLfSOrgHKskJWoEir0A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thursday, April 21, 2016, drum(dot)lucas(at)gmail(dot)com <drum(dot)lucas(at)gmail(dot)com>
wrote:
> So when I run:
>
> UPDATE ja_jobs t2
>> SET time_job = t1.time_job
>> FROM junk.ja_test t1
>> WHERE t2.id = t1.id
>> AND t2.time_job IS DISTINCT FROM t1.time_job;
>
>
> I get:
>
> UPDATE 2202
>
> So I check the data by doing:
>
> select * FROM public.ja_jobs WHERE id = 14574527
>
>
> And the "time_job" field is null....
>
>
Providing bits and pieces, without any data, is not going to get us
anywhere.
Create a self-contained test case the exhibits the problem.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Guyren Howe | 2016-04-21 20:36:54 | Proper relational database? |
| Previous Message | drum.lucas@gmail.com | 2016-04-21 18:52:58 | Re: Update field to a column from another table |