From: | "Ewan, Michael" <michael(dot)ewan(at)intel(dot)com> |
---|---|
To: | Rich Shepard <rshepard(at)appl-ecosys(dot)com>, "pdxpug(at)postgresql(dot)org" <pdxpug(at)postgresql(dot)org> |
Subject: | Re: Entering '<1' and 'BDL' |
Date: | 2010-04-20 17:38:10 |
Message-ID: | 66C9C47441840949A66773F8F0D9D6A7B01A6583@rrsmsx503.amr.corp.intel.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pdxpug |
As you noted, NULL will fit the bill for your NAN values, but make sure the table allows NULL's in that column and that your code handles NULL's either by skipping them (a self join can often help) or by converting them to 0 if you want them to count in the statistics.
> -----Original Message-----
> From: pdxpug-owner(at)postgresql(dot)org [mailto:pdxpug-owner(at)postgresql(dot)org]
> On Behalf Of Rich Shepard
> Sent: Monday, April 19, 2010 4:12 PM
> To: pdxpug(at)postgresql(dot)org
> Subject: [pdxpug] Entering '<1' and 'BDL'
>
> For a scientific database holding observed and measured values there
> are
> two non-numeric (NAN) legitimate entries: <1 and 'below detection
> limits.'
> Is anyone aware of a standard way of expressing these?
>
> The problem is that the column needs to be of a numeric type because
> the
> numbers will be manipulated mathematically and summarized
> statistically. So
> a NAN such as '<1' or 'BDL' doesn't cut it.
>
> Any thoughts?
>
> Rich
>
> --
> Richard B. Shepard, Ph.D. | Integrity
> Credibility
> Applied Ecosystem Services, Inc. | Innovation
> <http://www.appl-ecosys.com> Voice: 503-667-4517 Fax: 503-667-
> 8863
>
> --
> Sent via pdxpug mailing list (pdxpug(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pdxpug
From | Date | Subject | |
---|---|---|---|
Next Message | Rich Shepard | 2010-04-20 17:43:01 | Re: Entering '<1' and 'BDL' |
Previous Message | Melissa Hollingsworth | 2010-04-20 16:16:02 | Re: Entering '<1' and 'BDL' -- RESOLVED |