Re: Sql Oddity
- From: Stephane Faroult <sfaroult@xxxxxxxxxxxx>
- To: ilmar.kerm@xxxxxxxxx
- Date: Mon, 18 Jan 2010 21:51:54 +0100
Exactly my thought - I was just checking the docs when Ilmar answered,
SYSTIMESTAMP returns a TIMESTAMP WITH TIMEZONE, not a TIMESTAMP.
Stephane Faroult
RoughSea Ltd <http://www.roughsea.com>
RoughSea Channel on Youtube <http://www.youtube.com/user/roughsealtd>
Ilmar Kerm wrote:
>
>
> On Mon, Jan 18, 2010 at 10:26 PM, Goulet, Richard
> <Richard.Goulet@xxxxxxxxxxx <mailto:Richard.Goulet@xxxxxxxxxxx>> wrote:
>
> Folks,
>
> Anyone ever seen this: A developer executes the following
> code in an Oracle 9i database (9.2.0.6)
>
> create table test_date_drop_me (test_column timestamp default
> sysdate);
>
> insert into test_date_drop_me values (sysdate);
>
> select CASE WHEN systimestamp> t.test_column THEN 1 ELSE 0 END
> from test_date_drop_me t;
>
> He gets a 0 each time the final select statement is excecuted no
> matter what the value in the table. In a 10.2.0.4 and 11.1.0.7
> database we get a 1. Any ideas???
>
> */
> /*
>
> Could it be related to different time zones for the client and server?
>
> --
> Ilmar Kerm
> Sent from Tallinn, Harjumaa
--
//www.freelists.org/webpage/oracle-l
Other related posts:
