Handle ambiguous precision/scale on NUMERIC output

[mitalia]

With some databases, numeric output can come out of the database without precision and scale assigned. Currently, this causes table creation and inserts to fail. We should fall back to a plain NUMERIC data type with no precision or scale when this happens (if supported by the target database). There is an Oracle example we can use as a starting point.