Currently the CSV reader stores the whole file in memory before parsing it. This is a relict of refactoring the whole parser infrastructure several times during the early days of cutplace.
The proper solution would be to use a consumer/producer like for ODS, where the producer would read the CSV in a separate thread.
Currently the CSV reader stores the whole file in memory before parsing it. This is a relict of refactoring the whole parser infrastructure several times during the early days of cutplace.
The proper solution would be to use a consumer/producer like for ODS, where the producer would read the CSV in a separate thread.