Try casting the constant to the type of the field, i.e.
WHERE timestamp >= '7/12/2004'::"timestamp without time zone"
(iirc the quotes are necessary)
Also, I'd try to avoid naming attributes like (built-in) types. (iirc
"timestamp" is a type without time zone in 7.3, and with time zone in 7.4
I'd like to add that a NULL value might mess things up. If CreateTime may be
null, try this:
if (OLD.CreateTime <> NEW.CreateTime) OR
(OLD.CreateTime ISNULL <> NEW.CreateTime ISNULL) THEN ...
or this:
if COALESCE(OLD.CreateTime, '3001-01-01') <>
COALESCE(NEW.CreateTime, '3001-01-01
- Original Message -
From: "Greg Stark" <[EMAIL PROTECTED]>
Sent: Tuesday, October 28, 2003 7:21 PM
> > > cannot see is that the float values are not actually exactly 0.5
> >
> > Yes I could guess that (floating point vs fixed), but is this a
coincidence
> > that both '0.5'::float and '-
I have a php script that patches database, comparing pg_catalog's tables to
input files. One thing it can do, but I can't take responsibility ;) is
changing the type of a column.
It's basically the same that everyone wrote, except that I also examine
dependencies, as broad an examination as I coul
