Oracle is inconsistent in numbering of data types

[tmalaher]

Oracle TIMESTAMP data type is sometimes numbered as 180 and sometimes as 187,

See: https://community.oracle.com/thread/914475?tstart=0

And for the definitive list: https://ellebaek.wordpress.com/2011/02/25/oracle-type-code-mappings/

The fix is to change anywhere that the col_type is being compared to 187 to:
record_desc_table(col).col_type in (180, 187) (several places in get_json)
or in one case:
record_desc_table(col).col_type in (2,12,180,187)

Also, the DESCRIBE_COLUMNS3 procedure in Oracle now returns a col_type_name field, which may allow for the replacement of the numeric values with symbolic values that might be more portable.