From: | Jonathan Strong <jonathanrstrong(at)gmail(dot)com> |
---|---|
To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
Cc: | Igor Korot <ikorot01(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: How to write such a query |
Date: | 2020-09-18 18:24:12 |
Message-ID: | CAK8Y=HXz2B1WvYwovWu=7ksW9k8rbZgyNfsSD2q0+4OYxq-qpw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Yes - 100%
- Jon
<https://www.linkedin.com/in/jonstrong/>
<https://www.jonathanrstrong.com>
*Jonathan Strong*
CIO / CTO / Consultant
*P:* 609-532-1715 *E:* jonathanrstrong(at)gmail(dot)com
*Quora Top Writer <https://www.quora.com/profile/Jonathan-R-Strong>*
On Fri, Sep 18, 2020 at 2:22 PM Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
wrote:
> On 9/18/20 11:13 AM, Jonathan Strong wrote:
> > @Adrian -
> >
> > Using a unique key value or otherwise isolating a specific record via
> > selection against values in its attributes is certainly preferable to
> > choosing a row to update via its position in a result set, unless the
> > use case actually makes use of that position info as a meaningful
> > descriptor of the data in some fashion.
>
>
> The bigger issue is deciding what attribute of the selected row is be
> used to do the UPDATE. Unless it is the PRIMARY KEY(or other UNIQUE
> key(s)) then you very likely are going to UPDATE more then you bargained
> for.
>
> >
> > - Jon
> >
> > <https://www.linkedin.com/in/jonstrong/> <
> https://www.jonathanrstrong.com>
> >
> >
> >
> > *Jonathan Strong*
> >
>
>
> --
> Adrian Klaver
> adrian(dot)klaver(at)aklaver(dot)com
>
From | Date | Subject | |
---|---|---|---|
Next Message | Igor Korot | 2020-09-18 18:49:09 | Re: How to write such a query |
Previous Message | Jonathan Strong | 2020-09-18 18:23:46 | Re: How to write such a query |