| From: | Scott Ribe <scott_ribe(at)elevated-dev(dot)com> |
|---|---|
| To: | David Johnston <polobo(at)yahoo(dot)com> |
| Cc: | 'Grzegorz Jaśkiewicz' <gryzman(at)gmail(dot)com>, <condor(at)stz-bg(dot)com>, <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Real type with zero |
| Date: | 2011-06-29 16:19:05 |
| Message-ID: | F817EC5F-3A19-474A-82D9-E45BAB2B41C9@elevated-dev.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Jun 29, 2011, at 9:50 AM, David Johnston wrote:
> Aside from storing the "true" precision in a separate integer field what solution is there is this situation.
I think the only other way would be a custom data type encapsulating those 2 bits of info. Which might be the best solution, since if you really need to maintain info about the significant digits of measurements, you need that to carry through properly in calculations with those numbers.
OTOH, it's possible to have that info in a separate field, and leave with clients the responsibility for correct calculations...
--
Scott Ribe
scott_ribe(at)elevated-dev(dot)com
http://www.elevated-dev.com/
(303) 722-0567 voice
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jonathan S. Katz | 2011-06-29 16:24:28 | Re: point types in "DISTINCT" queries |
| Previous Message | Grace Batumbya | 2011-06-29 16:14:00 | Windows x64 : How do I get OSSP-UUID.sql contrib for postgresql x64 |