From: | Nabil Sayegh <postgresql(at)e-trolley(dot)de> |
---|---|
To: | Michal Lijowski <michal(at)cvu(dot)wustl(dot)edu> |
Cc: | pgsql-novice(at)postgresql(dot)org |
Subject: | Re: Using SELECT WHERE |
Date: | 2004-04-20 18:06:41 |
Message-ID: | 408566B1.8030503@e-trolley.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
The given expression could be interpreted as a timestamp.
Try casting it explicitly to date:
... WHERE implantdate!='0001-01-01'::date ...
but that's just a guess.
HTH
Michal Lijowski wrote:
> RabStudies=> SELECT RabNo, ImplantDate, Comments FROM RabStudiesInfo
> where implantdate <> 0001-01-01;
>
> and I get
>
> rabno | implantdate | comments
>
> 307 | 2004-02-23 | No mimetic No target
> 309 | 2004-02-23 | No mimetic No target; Frame 12 study terminated
> 314 | 2004-02-27 | No mimetic No target
> 311 | 2004-02-27 | No mimetic No target
> 310 | 2004-02-26 | No mimetic No target No decoy
> 315 | 0001-01-01 | No Tumor
> 320 | 0001-01-01 | No Tumor
> 316 | 0001-01-01 | No Tumor
> 313 | 0001-01-01 | No Tumor
>
> Why entries with implandate are listed?
> It is the same when I use != instead of <>.
--
e-Trolley Sayegh & John, Nabil Sayegh
Tel.: 0700 etrolley /// 0700 38765539
Fax.: +49 69 8299381-8
PGP : http://www.e-trolley.de
From | Date | Subject | |
---|---|---|---|
Next Message | Bruno Wolff III | 2004-04-20 18:17:03 | Re: question on forced-killing the postmaster |
Previous Message | Bruno Wolff III | 2004-04-20 18:04:55 | Re: Using SELECT WHERE |