[root]/PZFileReaderSamples/src/main/java/net/sf/pzfilereader/examples
createsamplecsv
(1 files, 98 lines)
csvheaderandtrailer
(1 files, 73 lines)
csvperformancetest
(1 files, 147 lines)
delimitedcolumnnamesinfile
(1 files, 60 lines)
delimiteddynamiccolumns
(1 files, 95 lines)
delimiteddynamiccolumnswitherrors
(1 files, 91 lines)
exporttoexcel
(1 files, 69 lines)
fixedlengthdynamiccolumns
(1 files, 53 lines)
fixedlengthheaderandtrailer
(1 files, 85 lines)
jsptableexample
(0 files, 0 lines)
pzfilereaderwebsamples
(1 files, 113 lines)
largedataset
(0 files, 0 lines)
delimiteddynamiccolumns
(1 files, 75 lines)
fixedlengthdynamiccolumns
(1 files, 59 lines)
largecsvperformancetest
(1 files, 125 lines)
lowlevelparse
(1 files, 80 lines)
multilinedelimitedrecord
(1 files, 60 lines)
numericsanddates
(1 files, 56 lines)
| Author | Changes | Lines of Code | Lines per Change |
|---|---|---|---|
| Totals | 13 (100.0%) | 125 (100.0%) | 9.6 |
| Benoit Xhenseval | 11 (84.6%) | 120 (96.0%) | 10.9 |
| Paul Zepernick | 2 (15.4%) | 5 (4.0%) | 2.5 |
removed 1.5 only StringBuilder
1 lines of code changed in:
fixed compilation errors from removal of LargeDataSet
4 lines of code changed in:
Paul, some interesting new methods, the BX parser (sorry about the name) seems to be significantly faster than the current one when there are NO qualifiers, If there are qualifiers, it is reasonably faster. But the interesting bits start when I created a new method that uses a StringBuffer rather than using "chunks".
The new method is flying when there are qualifiers all over the place... but is slower (albeit not slower than the current one) when there are no qualifier... and that is a bit of a mystery... anyway... getting too late... Have a look and let me know.
11 lines of code changed in:
Added an option (17) to compare the BX parser and the current parser.
It should be noted that the current parser fails on some tests (Paul could you fix?)
Just select the number of repeat, the number of columns and whether the column should be qualified or not... tell me your results. ta
40 lines of code changed in:
Added a heuristic test that proves that using a StringBuffer delete is better than creating a new one...
60 lines of code changed in:
Some serious kicking...
1/ use a map for finding the column index; this makes the fetch of the first or last column consistent
2/ removed SOME of the substring which are causing dramatic performance degradation when once has a fair amount of columns.
3/ optimised some string manipulation code (getDelimiterOffset, lTrim, lTrimKeepTabs, removeChar
4/ I would suggest the creation of a suite of unit tests for all those methods.... Paul, do you want to take this on?
8 lines of code changed in:
Couple of changes for website.
1 lines of code changed in:
Moved to net.sf.pzfilereader
0 lines of code changed in:
