| From: | Kris Jurka <books(at)ejurka(dot)com> |
|---|---|
| To: | dombrd(at)gmail(dot)com |
| Cc: | pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: Correct getScale() behavior? |
| Date: | 2008-05-09 19:45:24 |
| Message-ID: | Pine.BSO.4.64.0805091536060.13570@leary.csoft.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
On Fri, 9 May 2008, dombrd(at)gmail(dot)com wrote:
> I realize I'm not going to get you to change back to returning -1 for
> the scale and precision, because a lot of users would be affected by
> that. However, I am wondering if there is a way we could get the
> actual precision and scale returned for an aggregate sum, and other
> aggregate functions as well.
>
> I would think it should be returning a scale and precision if the
> argument column has scale and precision specified, such as in the
> NUMERIC(7,2) example I previously showed. It seems wrong to return 0
> in this case.
>
> I am guessing the postgresql server code would need to be changed for
> that to work though. Maybe I should be suggesting this change on a
> different list?
>
Right, that change would be nice, but it would require a server change.
The best place to ask about that would be -hackers. Also how do you
determine the precision of sum(numeric(7,2))?
Kris Jurka
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-05-10 00:09:06 | Re: Correct getScale() behavior? |
| Previous Message | Kris Jurka | 2008-05-09 19:36:02 | Re: Couple of preparedstatement bug suspects |