From: | Francisco Olarte <folarte(at)peoplecall(dot)com> |
---|---|
To: | Karsten Hilbert <Karsten(dot)Hilbert(at)gmx(dot)net> |
Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: [EXTERNAL]: Re: [EXTERNAL]: Re: UPSERT in Postgres |
Date: | 2023-04-10 11:33:41 |
Message-ID: | CA+bJJbxebcpxEA=Y2L90p5PvTU1j5sMi5J5eyEwe-T3Qr0ZThw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi karsten:
On Mon, 10 Apr 2023 at 11:40, Karsten Hilbert <Karsten(dot)Hilbert(at)gmx(dot)net> wrote:
>
> Am Mon, Apr 10, 2023 at 09:41:15AM +0200 schrieb Francisco Olarte:
>
> > On Mon, 10 Apr 2023 at 04:16, Rob Sargent <robjsargent(at)gmail(dot)com> wrote:
> > > > An UPSERT checks whether a row exists, if so, it does an update, if not it does an insert. This is the literal definition.
> > > This the part that's always eluded me: How does the client, the
> > > UPSERTer, come to hold an id and not know whether or not it's already in
> > > the database.
> >
> > This is extremely easy to do if you have natural instead of surrogate keys.
> >
> > I work in telephony, upserting the last incoming call timestamp for a
> > phone number will be exactly that.
>
> timezones ?
> DST ?
A timestamp is a point in the time line, this is what I insert, just a
real number marking a line, timezones and dst are presentation stuff.
> spoofing ?
¿ Of what ? I do it for a phone number, not for a customer, it does
not matter to me if the number came from a legit customer or from a
spoofer, I want it for the phone number.
Francisco Olarte.
From | Date | Subject | |
---|---|---|---|
Next Message | Karsten Hilbert | 2023-04-10 12:35:38 | Re: [EXTERNAL]: Re: [EXTERNAL]: Re: UPSERT in Postgres |
Previous Message | Amit Kapila | 2023-04-10 11:20:09 | Re: Support logical replication of DDLs |