> > OK, I hear ya. How about allowing user to set the default precision and
> > scale values for "numeric" type? Not sure how this would be done in JDBC
> > world but should be doable.
>
> You could add URL parameters like unspecifiedNumericPrecision=1000 and
> unspecificedNumericScale=500, but the tradeoff is how much work is it to
> add these options to the URL parsing code and then pass them around, add
> it to the datasource implementation, add it to the documentation, and ...
>
> If there was some big important app that everyone wanted to use that blew
> up on this I'd bet we'd do it, but I haven't heard a whole lot of
> complaints about this problem.
I would assume this is not a major issue for most. Personally I ran into
this problem when writing automated PG->MS Access converter (Jackcess is
the only lib capable of creating MDB files on Linux/BSD) and it bailed
on numeric fields.
Peter
