Hi team, is it time to soon do a release? I guess we need to update the version log with all the stuff. Currently 44 commits have been made since last release.

Add a writer to write a JDBC ResultSet as CSV.

CsvResultSetWriter writes a CSV file by mapping each column of the ResultSet to a column in CSV file using column names stored in ResultSetMetaData. It can be used with or without CellProcessors.

Closes issue #6.

An idea could be to create a unit test called "FeaturesOfSuperCsv" which has a test for each row of the comparison matrix showing that supercsv in fact has this feature. Missing features should be made into individual issues which the community then can implement or reject.

this test is nice for

• new people on the team
• people doing comparisons
• for linking from the documentation pages

features to show can be found in

• the existing documentation
• http://csveed.org/comparison-matrix.html
• https://github.com/uniVocity/csv-parsers-comparison

Add additional overloaded read() methods to CsvBeanReader that accepts column name mappings and cell processors as maps instead of arrays. The new methods:

• allows to read beans directly from CSV when CSV headers are different than bean field names
• has no dependency on columns number or order
• are more convenient in case of CSV files with large number of columns

Closes issue #65

This is meant to support reading data where the quote escape character is not the RFC-compliant second quote character, but instead a separate escape character, commonly a backslash ''.

RFC-compliant row:

one,"two","three with a "" quote character",four

Row this PR is meant to support:

one,"two","three with a \" quote character",four

We want to be able to parse both to this resulting list:

[one, two, three with a " quote character, four]

General definition for the quoteEscapeChar is:

• By default the quoteEscapeChar is set to the quoteChar
• To write an escape char into actual data, double the escape char
• An escape char before normal data results in both chars being passed through
• Continue to write data in normal RFC-compliant

Please see additional unit tests written to support this feature and note that no existing unit tests needed to be modified to support this new option, indicating the existing behavior is unchanged.

Fixes https://github.com/super-csv/super-csv/issues/14

Hi,

I have created default parsers and formatters for the JSR310 date types https://github.com/ludovicofischer/super-csv-jsr310. Would you be interested in having it inside the main supercsv repository like the Joda formatters? The code is a port of the joda extras. It works but it needs some more testing.

Hi,

I have a problem using supercsv. Sometimes, I have to deal with some "incorrect" CSV files like that :

"header1";"header2" "value1";"value2";

As you can see, I have 2 headers and 3 values in the second line. This prevent me from doing a partial read. This is the same case when executing CellProcessors.

Is it ok for you ?

Super CSV doesn't work when your locale is Turkey: reflection fails because it looks for getters/setters in the format: setİsActive /getİsActive (not the capital I is not normal).

There's so many places in the code where this could be an issue that I'm reluctant to attempt to make Super CSV pass the Turkey Test - I don't think Dozer would pass this test either. But if this ticket gets enough love then we could look at it.

Originally raised on SourceForge

Hi, I implemented the new ParseTime to convert String to Time Objects. I created an abstract class (ParseDateTimeAbstract) extended by ParseDate and ParseTime. I modified also JUnit test adding the birthTime to PersonBean.

Pietro

Super CSV escapes embedded quotes per RFC4180, e.g.

"This is what ""embedded quotes"" look like"

Some CSV files don't adhere to RFC4180, and use a \ (backslash) character instead 2 quote characters, e.g.

"This is what \"embedded quotes\" look like"

Add an escapeCharacter preference (defaults to quoteCharacter) that allows for this (with a disclaimer that it makes CSV less portable and doesn't comply with RFC4180.

Originally raised as Feature Request 42 on SourceForge.

In project we have Eclipse code-style configuration file - supercsv_eclipse_formatter.xml. I think, it would be great if we could create the same for IntelliJ and add it to project.

Requirements:

1. Code formatted in Eclipse and IntelliJ should looks the same.

The existing package is fairly old. What are peoples preference in terms of minimum required java version for the next version? Which language features should be leveraged? E.g. Modules.

Recently brought an ancient project up to date and now blanks are no longer trimmed (great btw) my tests discovered that chaining is broken for ConvertNullTo.

It's implementation of the execute should be:

public <T> T execute(final Object value, final CsvContext context) {
	if (value == null) {
		return next.execute(returnValue, context);
	}
	
	return next.execute(value, context);
}

(the 3rd line is normally return returnValue;)

To test it, just use a cell processor like: new ConvertNullTo("-1", new ParseLong())

Thanks for Super CSV btw, I love it :-) (which is why I bothered raising the issue, because I could easily fix it locally).

Bumps h2 from 1.3.171 to 2.1.210.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Unfortunately, due to unfortunate naming, SuperCSV 2.4.0 can't be used in modularized projects:

[WARNING] Can't extract module name from super-csv-2.4.0.jar: super.csv: Invalid module name: 'super' is not a Java identifier

This PR adds explicit modules:

• Project is migrated to Java 9.
• The java8 folder is merged to the main project.

The assertEquals(...) calls in tests were ambiguous. For example, when called with (long, Long) parameters, both assertEquals(Object,Object) and assertEquals(long,long) were applicable. This PR makes the calls unambiguous.