# Enhancement Request - ARP JDBC Data Type Mapping

**URL:** https://community.dremio.com/t/enhancement-request-arp-jdbc-data-type-mapping/5032
**Category:** Uncategorized
**Created:** [February 11, 2020, 4:04pm UTC](https://community.dremio.com/t/enhancement-request-arp-jdbc-data-type-mapping/5032 "2020-02-11T16:04:54Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![patricker](https://sea2.discourse-cdn.com/flex020/user_avatar/community.dremio.com/patricker/32/1823_2.png) [@patricker](https://community.dremio.com/u/patricker)
#### Post date: [February 11, 2020, 4:04pm UTC](https://community.dremio.com/t/enhancement-request-arp-jdbc-data-type-mapping/5032/1 "2020-02-11T16:04:54Z")

</div>

When mapping data types, date and timestamp objects need to support NOT passing in a calendar object to the `getDate` and `getTimestamp` methods. In my scenario, the JDBC driver just doesn’t implement these versions of the methods and only supports calling the non-Calendar method.

Something like the `enable_utc_calendar` option shown below.

- source:  
name: “DATE”  
enable\_utc\_calendar: false  
dremio:  
name: “date”
- source:  
name: “TIMESTAMP”  
enable\_utc\_calendar: false  
dremio:  
name: “timestamp”