Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: numeric type
- From: Kris Jurka <books(at)ejurka(dot)com>
- To: Peter <peter(at)greatnowhere(dot)com>
- Cc: pgsql-jdbc(at)postgresql(dot)org
- Subject: Re: numeric type
- Date: Tue, 29 Jul 2008 13:09:56 -0400 (EDT)
- Message-id: <Pine.BSO.4.64.0807291305500.32353@leary.csoft.net> <text/plain>
On Tue, 29 Jul 2008, Peter wrote:
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.
Is this an important issue for other people? Kris Jurka
- Follow-Ups:
- Re: numeric type
- From: Peter Zeltins
- Re: numeric type
- References:
- numeric type
- From: Peter
- Re: numeric type
- From: Kris Jurka
- Re: numeric type
- From: Peter
- numeric type
- Prev by Date: Best practise on closing connections in programs of unkown/unexpectedly long durations
- Next by Date: Re: GSSAPI/KRB5 and JDBC (again)
- Previous by thread: Re: numeric type
- Next by thread: Re: numeric type
- Indexes: