On 10-Mar-2016 09:15 -0600, John Yeung wrote:
<<SNIP>> I feel there ought to be more sophisticated determination of
when to implicitly clear a file. Like maybe if the total (active plus
deleted) records is over a certain threshold, then attempt to clear.
(If this is already the case and my testing just didn't hit it, then
the threshold is too high.)
FWiW: re old message thread
[
http://archive.midrange.com/midrange-l/201603/threads.html#00292]
If the issue with the algorithm accounting for only the
active-record-count vs the total-record-count is considered [by you to
be] a defect, then open a PMR. Otherwise, perhaps either make a comment
on the documentation page that in-part describes the algorithm [quoted
in at least two replies, but I do not recall any links], asking for
clarification on the threshold for a SQL DELETE request affecting a
"large" number of rows and for why inactive rows are not included, or
submit a Design Change Request asking that members with "many" deleted
rows should also meet the threshold for the effective CLRPFM or CHGPF.
Changes are unlikely to occur if change is not requested; the
architects\designers\programmers are not poring over this list\NG
looking for messages that might appear to qualify as RFEs, and thus
probably should be considered for possible DCRs.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.