In the real world it's probably negligible. I almost always use READWRITE.
--
rk
-----Original Message----- From: ProfoxTech profoxtech-bounces@leafe.com On Behalf Of MB Software Solutions, LLC Sent: Wednesday, June 24, 2020 10:25 PM To: profoxtech@leafe.com Subject: Re: Bizarre scenario solved by READWRITE clause on end of SELECT SQL
On 6/24/2020 5:35 PM, Richard Kaye wrote:
If you don't need the overhead of a writable cursor you can also use NOFILTER to force the query engine to not just do a USE...AGAIN with a filter. As for why now, the simplest answer I can think of is there was something about the query and the source data where Rushmore decided the latter strategy was the best way to give the desired results.
I've honestly never used the NOFILTER clause. How much overhead does READWRITE cause vs. the NOFILTER I wonder? Are we again talking about something negligible?
-- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
_______________________________________________ Post Messages to: ProFox@leafe.com Subscription Maintenance: https://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: https://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: https://leafe.com/archives This message: https://leafe.com/archives/byMID/a0003bb4-5356-d95d-7e7a-121d122e965d@mbsoft... ** 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. Report [OT] Abuse: http://leafe.com/reportAbuse/a0003bb4-5356-d95d-7e7a-121d122e965d@mbsoftware...