ALL RECORDS + DELETE SELECTION, or selecting all records and deleting them in User Mode logs "delete" action for each record in the journal file.
TRUNCATE TABLE, on the other hand, has its own single action in the journal file. "Truncate" clears the address table, whereas "Delete" does not. the main advantage of keeping the same (fragmented) address table is that saves sets continue to work after a data compact. the disadvantage is that isolated addresses may take longer to locate. c.f http://kb.4d.com/assetid=76195 http://kb.4d.com/assetid=76209 http://kb.4d.com/assetid=76414 tip: search for "compact@" at kb.4d.com to find articles that refer to compacting. typically one would end up with a fragmented address table when a table with a relatively low number of records has had a high record count some time in the past. (the address count corresponds to the peak count) a2017/04/05 2:43、Charles Miller via 4D_Tech <[email protected]> のメール： > > I seem to remember a tech note or example that would fix index problems > that you would have when deleting most of the record in a able or or > truncating it. ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
