Re: [EXTERNAL]: Re: [EXTERNAL]: Re: UPSERT in Postgres - Mailing list pgsql-general

From Karsten Hilbert
Subject Re: [EXTERNAL]: Re: [EXTERNAL]: Re: UPSERT in Postgres
Date
Msg-id ZDPZadH7FJDh1RcB@hermes.hilbert.loc
Whole thread Raw
In response to Re: [EXTERNAL]: Re: [EXTERNAL]: Re: UPSERT in Postgres  (Francisco Olarte <folarte@peoplecall.com>)
Responses Re: [EXTERNAL]: Re: [EXTERNAL]: Re: UPSERT in Postgres
List pgsql-general
Am Mon, Apr 10, 2023 at 09:41:15AM +0200 schrieb Francisco Olarte:

> On Mon, 10 Apr 2023 at 04:16, Rob Sargent <robjsargent@gmail.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 ?

spoofing ?

...

Karsten
--
GPG  40BE 5B0E C98E 1713 AFA6  5BC0 3BEA AC80 7D4F C89B



pgsql-general by date:

Previous
From: Allan Nielsen
Date:
Subject: Re: Patroni vs pgpool II
Next
From: Francisco Olarte
Date:
Subject: Re: [EXTERNAL]: Re: [EXTERNAL]: Re: UPSERT in Postgres