Hi Rick, Isn't the use of ALL redundant when using the FOR scope in a REPLACE statement as the FOR scope will force the replace to evaluate each row, right? Unless you use FOR with REST? What is the locking scheme under those conditions - header or record?
-- rk -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Rick Schummer Sent: Wednesday, April 25, 2012 2:49 PM To: [email protected] Subject: RE: lockng issues >> REPLACE post_date WITH date() FOR post_date <> date() ALL in >> YourTableName<< Two comments: 1) REPLACE ALL places a header lock, where SCAN...ENDSCAN and REPLACE uses record locking 2) Depending on the time of the process (around midnight), it is entirely possible your use of DATE() could produce different dates using this one command. If all the dates being the same are important you should get the date to a memvar and use that in the replace. Rick White Light Computing, Inc. www.whitelightcomputing.com www.swfox.net www.rickschummer.com [excessive quoting removed by server] _______________________________________________ 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 Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/DF1EEF11E586A64FB54A97F22A8BD0441D52CAC5F8@ACKBWDDQH1.artfact.local ** 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.
