From: | <hagen(at)datasundae(dot)com> |
---|---|
To: | "'David G(dot) Johnston'" <david(dot)g(dot)johnston(at)gmail(dot)com> |
Cc: | <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | RE: INSERT Trigger to check for existing records |
Date: | 2020-11-21 18:49:06 |
Message-ID: | 000e01d6c036$fda479b0$f8ed6d10$@datasundae.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Yes but it didn’t sink in but the two table join idea does make sense – I’ll give that a try. THANK YOU.
From: David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>
Sent: Saturday, November 21, 2020 11:25 AM
To: Hagen Finley <hagen(at)datasundae(dot)com>
Cc: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: INSERT Trigger to check for existing records
On Saturday, November 21, 2020, David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com <mailto:david(dot)g(dot)johnston(at)gmail(dot)com> > wrote:
On Saturday, November 21, 2020, Hagen Finley <hagen(at)datasundae(dot)com <mailto:hagen(at)datasundae(dot)com> > wrote:
David,
That's an interesting idea. I WOULD like to retain the OLD records that are the same and only INSERT new or changed records. Is there a way to compare the old and the new records without a trigger?
A where clause?
Did you get the part in the plan where there are two tables, existing and new? You write queries that join the two tables together and use the where clause in those queries to limit records.
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Lewis | 2020-11-22 15:54:38 | Re: INSERT Trigger to check for existing records |
Previous Message | David G. Johnston | 2020-11-21 18:24:34 | Re: INSERT Trigger to check for existing records |