Re: [EXTERNAL]: Re: [EXTERNAL]: Re: UPSERT in Postgres
От | Francisco Olarte |
---|---|
Тема | Re: [EXTERNAL]: Re: [EXTERNAL]: Re: UPSERT in Postgres |
Дата | |
Msg-id | CA+bJJbxebcpxEA=Y2L90p5PvTU1j5sMi5J5eyEwe-T3Qr0ZThw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [EXTERNAL]: Re: [EXTERNAL]: Re: UPSERT in Postgres (Karsten Hilbert <Karsten.Hilbert@gmx.net>) |
Ответы |
Re: [EXTERNAL]: Re: [EXTERNAL]: Re: UPSERT in Postgres
|
Список | pgsql-general |
Hi karsten: On Mon, 10 Apr 2023 at 11:40, Karsten Hilbert <Karsten.Hilbert@gmx.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@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 ? 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.
В списке pgsql-general по дате отправления: