JDBC Type Mapping

Overview

There are four strategies in DataPipeline v8.0+ to map JDBC/database types to fields in records.

1. OPINIONATED - the default mapping type using our preferred algorithm. This strategy uses the types in java.sql.Types along with other properties (like size, decimals, and other metadata).
2. STRICT - the mapping defined by Oracle/Sun and implemented as the default by most JDBC drivers. This strategy uses the types in java.sql.Types alone.
3. ORIGINAL - the mapping used by DataPipeline prior to version 8.0. This strategy is similar to OPINIONATED with improvements after analyzing the behavior of several databases and drivers
4. custom - your own custom, programmed mapping.

JDBC Type Mapping Examples

1. Read from database using OPINIONATED type mapping
2. Read from database using STRICT type mapping
3. Read from database using ORIGINAL, pre-version 8.0 type mapping

Custom Type Mappings

You can build a custom mapping by implementing com.northconcepts.datapipeline.jdbc.JdbcValueReader and passing it to JdbcReader.setValueReader(JdbcValueReader).

Built-In Type Mappings