Re: Interval constant syntax, was Re: Interval & check clause - Mailing list pgsql-general

From Karl O. Pinc
Subject Re: Interval constant syntax, was Re: Interval & check clause
Date
Msg-id 20040329152859.M9609@mofo.meme.com
Whole thread Raw
In response to Re: Interval constant syntax, was Re: Interval & check clause  (Bruno Wolff III <bruno@wolff.to>)
Responses Re: Interval constant syntax, was Re: Interval & check
Re: Interval constant syntax, was Re: Interval & check clause
List pgsql-general
On 2004.03.29 14:44 Bruno Wolff III wrote:
>
> In postgres you shouldn't have to explicitly cast the constant to an
> interval as long as there isn't one than one >= operator that could
> be applied (depending on the eventaul type of the constant). I would
> really be surprized if this were to happen for >= and an interval
> operand
> on one side or the other.
>
> It won't work with two unknown constants, if that was what you tested.
> Try just casting on one side.

This is my plpgsql code

  PERFORM MATUREDATES.sname FROM MATUREDATES
     WHERE NEW.sname = MATUREDATES.sname
           AND ( NEW.birth > MATUREDATES.Matured - ''3 years''
                 OR NEW.birth > MATUREDATES.Matured - ''7 years'');
   IF FOUND THEN

And this was my scratch psql test:

=> select CAST('1/1/2004' AS date) - '3 years';
ERROR:  Bad date external representation '3 years'

I am using 7.3 so maybe this has been fixed.  Or it's just the
operator, some require casts and some don't and you just have to find
out the hard way.  :(

Karl <kop@meme.com>
Free Software:  "You don't pay back, you pay forward."
                  -- Robert A. Heinlein

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: PG vs MySQL
Next
From: "scott.marlowe"
Date:
Subject: Re: PG vs MySQL