For numeric types (with no explicit scale and precision) JDBC returns 0 for both precision and scale (ResultSetMetaData.getPrecision and getScale methods). This is breaking my app and IMO does not reflect true state of things since Postgres docs state: „NUMERIC without any precision or scale creates a column in which numeric values of any precision and scale can be stored, up to the implementation limit on precision”.
Shouldn’t PG JDBC driver return maximum possible values for precision and scale in such cases?
