Input field ISI importer is too limited
I tried to parse 299 files, which I had stored in a folder 7 layers down from the root. Each file had an address that looked like this: E:\Projects\Drinkwatersector en Lissabon doelstelling\Data\ISI\ruwe data\final set\2006-2008\KWR-Watertech-final-3a-31July-2006-2008-7001-7500.txt. As it turns out, the input field of the ISI Importer only accepts 32767 (2^15-1) characters and as a result, after an hour or so of parsing, it had not imported all the files. So there are two issues:
--A more efficient method of inputting files for parsing.
--A better overview of the selected files: I couldn't tell which files it had or had not done.
--A more efficient method of inputting files for parsing.
--A better overview of the selected files: I couldn't tell which files it had or had not done.
Leave a comment
I will look for a workaround, but I think the basis of the problem is a limitation of windows itself.
on 2009-09-28 16:18 *
By Edwin_Horlings
Why would you let Windows dictate the limits of your programme?
Ideally, the parser would present you with a list of files with tick boxes to include or exclude.
Ideally, the parser would present you with a list of files with tick boxes to include or exclude.
The bug was real and caused by the file selector component itself. The problem was in a limitation of the length of the string set in the dropdown box.