RE: [PyDB2-discuss] inconsistency

[Atli T. <at...@ga...>]

That's correct. I have to use a different time duration for this to work
with pydb2 like
current timestamp - decimal(030000,6) which is a bitch because I am actua=
lly
porting a bunch of sql code from ingres and the less I have to change the
better.

	Atli

-----Original Message-----
From: yu...@ad... [mailto:yu...@ad...]
Sent: 28. ma=ED 2004 10:48
To: at...@ga...
Cc: pyd...@li...
Subject: Re: [PyDB2-discuss] inconsistency


Quoting Atli Thorbjornsson <at...@ga...>:

> Hi,
> 	I am dealing with an inconsistency between replies from db2. The
following
> comparison works fine using db2 command line
>
> select ... from ... where a.time >=3D CURRENT TIMESTAMP - '3 hours'
>
> but when using pydb2 I get:
>
> SQLSTATE : 42818, NATIVE ERROR CODE : -401
> [IBM][CLI Driver][DB2/6000] SQL0401N  The data types of the operands fo=
r
the
> operation ">=3D" are not compatible.  SQLSTATE=3D42818
>
> Any ideas?
> 	Atli Thorbjornsson.
I'm assuming that a.time is defined to be of type timestamp, right ?

-------------------------------------------------
This mail sent through IMP: http://horde.org/imp/