# Mapping for INTEGER on Oracle changed between Liquibase 2 and 3

**URL:** <https://forum.liquibase.org/t/mapping-for-integer-on-oracle-changed-between-liquibase-2-and-3/2935>\
**Category:** General Discussion\
**Created:** [March 17, 2014, 8:32pm UTC](https://forum.liquibase.org/t/mapping-for-integer-on-oracle-changed-between-liquibase-2-and-3/2935 "2014-03-17T20:32:00Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![michael.dick](https://avatars.discourse-cdn.com/v4/letter/m/a3d4f5/32.png) [@michael.dick](https://forum.liquibase.org/u/michael.dick)\
**Post date:** [March 17, 2014, 8:32pm UTC](https://forum.liquibase.org/t/mapping-for-integer-on-oracle-changed-between-liquibase-2-and-3/2935/1 "2014-03-17T20:32:00Z")

</div>

link cited in that post helps migrate from MySQL to Oracle, and doesn’t match the JDBC spec (or at least doesn’t match the links I provided above).

Is there a way use the more portable INTEGER type, or at least move back to NUMERIC(38,0) ?&nbsp;

Thanks,

-Michael Dick

---

<div class="post-metadata">

**Author:** ![nvoxland](https://avatars.discourse-cdn.com/v4/letter/n/87869e/32.png) [@nvoxland](https://forum.liquibase.org/u/nvoxland)\
**Post date:** [March 17, 2014, 8:32pm UTC](https://forum.liquibase.org/t/mapping-for-integer-on-oracle-changed-between-liquibase-2-and-3/2935/2 "2014-03-17T20:32:00Z")

</div>

Thanks, I created&nbsp;[https://liquibase.jira.com/browse/CORE-1836](https://liquibase.jira.com/browse/CORE-1836) to track the change.

Data type mapping is something that isn’t as clean as I woud like and I am planning on addressing in the near future.&nbsp;

For now, your easiest option is to use changelog parameters and use something like&nbsp;Nathan