Stephen the Cook wrote: > Tracy Pearson <> wrote: > >> Are you handling multi-user contentions? >> User1 gets data, interrupted by phone >> User2 gets data, makes change to field1, saves update >> User1 makes change to field2, saves update >> >> Does User1 save overwrite field1 again? >> >> Tracy >> >> -----Original Message----- >> From: MB Software Solutions >> Sent: Wednesday, March 28, 2007 2:21 PM >> >> None that stand out in my head at present! >> > > If you are making your update statement in a dynamic way, why not update the > columns that changed and your where clause is everything that didn't change. > > > Update ThatTable > Set col4= NevVal4 > , col6 = newVal6 > Where key = key > And col2 = oldVal2 > And col3 = oldVal3 > And col5 = oldVal5 > And col7 = oldVal7 > > KISS at work. >
Yep...I've seen code where they construct the UPDATE SQL on the fly with that kind of logic. -- Michael J. Babcock, MCP MB Software Solutions, LLC http://mbsoftwaresolutions.com http://fabmate.com "Work smarter, not harder, with MBSS custom software solutions!" _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
