why mload accepts duplicates and why dont fastload - response (1) by dnoeth

FastLoad is older than MLoad, when FL was implemented there was no MultiSet table in Teradata, yet.
This has been added later due to Standard SQL.
FastLoad doesn't know if a row is duplicate because it's an actual duplicate row or because there was a restart and the same row has been sent a second time. FL stores data directly in the target table and there's no place to store that kind of information.
If this feature was added it would mean more overhead/addidional space usage/slowing down the load and then it's no longer faster than MLoad. And why implementing this when there's already a tool (MLoad) which has this feature?
Btw, FL will load duplicates into a NoPI table (because there's no sort involved).
Dieter