Yes - 100% - Jon
<https://www.linkedin.com/in/jonstrong/> <https://www.jonathanrstrong.com> *Jonathan Strong* CIO / CTO / Consultant *P:* 609-532-1715 *E:* jonathanrstr...@gmail.com *Quora Top Writer <https://www.quora.com/profile/Jonathan-R-Strong>* On Fri, Sep 18, 2020 at 2:22 PM Adrian Klaver <adrian.kla...@aklaver.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.kla...@aklaver.com >
