Ambigous Method Invocation for Boxed / Non-Boxed Types

[bytefish]

I have a problem with the current API design, which also made me rewrite some functions in PgBulkInsert. We support both writing mapInteger with an Integer and a primitive int. This is done by using a custom Lambda "ToInt" function. But this leads to the ugly side-effect, that the JVM cannot resolve the correct method:

Basically I would like to rename the methods to:

• mapBooleanPrimitive
• mapFloatPrimitive
• ...

So this would not happen anymore. And one can easily choose to use the boxed / unboxed type.

[bytefish]

The reason to change it is also related to Issue #17. All columns have to be mapped, so there should be a simple way to assign default values to the column. If we are renaming to "mapIntegerPrimitive" for example, I can easily write something like this in a column: