Topic
IC4NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
1 reply Latest Post - ‏2013-10-03T19:20:31Z by GlennSkinner
Bzoo
Bzoo
67 Posts
ACCEPTED ANSWER

Pinned topic Interpretation of “TODAY ” in Clearquest

‏2013-10-03T18:31:54Z |

All:

CQ Windows Client (OS = Vista Enterprise)

Start_time=TODAY   is interpreted the same way in both 7.0.1.2 and  7.1.2.08

But, Start_time >TODAY   is interpreted differently in the above versions.

Please look below for the code.

Which one is correct ?

Can some body help me  with this?

 

Thanks in advance.

Bzoo

----------------------------------------------------------------

CQ Windows Client (OS = Vista Enterprise)

Version =7.0.1.2

---------------------------------------------------------------------

When I use "Start_time = TODAY" in CQ Query, I get the following SQL code

select distinct T1.dbid,T1.end_time,T1.id,T1.start_time from    Defect    T1 where T1.dbid <> 0 and

(T1.start_time >= {ts '2013-10-03 04:00:00'} and T1.start_time < {ts '2013-10-04 04:00:00'})

When I use "Start_time > TODAY" in CQ Query, I get the following SQL code

select distinct T1.dbid,T1.end_time,T1.id,T1.start_time from  Defect  T1 where T1.dbid <> 0 and

(T1.start_time > {ts '2013-10-03 04:00:00'})

 

CQ Windows Client (OS = Vista Enterprise)

Version= 7.1.2.08

 

When I use "Start_time = TODAY" in CQ Query, I get the following:

select distinct T1.dbid,T1.id,T1.end_time,T1.start_time from    Defect    T1 where T1.dbid <> 0 and

T1.start_time >= {ts '2013-10-03 04:00:00'} and T1.start_time < {ts '2013-10-04 04:00:00'})

 

When I use "Start_time > TODAY" in CQ Query, I get the following:

select distinct T1.dbid,T1.id,T1.end_time,T1.start_time from    Defect    T1 where T1.dbid <> 0 and

(T1.start_time > {ts '2013-10-04 03:59:59'})

 

 

  • GlennSkinner
    GlennSkinner
    58 Posts
    ACCEPTED ANSWER

    Re: Interpretation of “TODAY ” in Clearquest

    ‏2013-10-03T19:20:31Z  in response to Bzoo

    There were a number of issues with date-time fields fixed in the 7.1 stream. If you look at the SQL output from your 7.0.1.2 client. You will see that it is actually querying on dates equal to or greater than today, not just greater than. The query from the 7.1.2.8 client is correctly querying on tomorrow or greater. Time is now stored in UTC time in the Clearquest backend. I am making the assumption this query was created on the east coast which is currently 4 hours from UTC. So the query is looking for a start_time greater than '2013-10-03 23:59:59'which is correct.

    If you did not create the query in the eastern time zone. Would you let me know what time zone it was created, and confirm that this was the clearquest for windows client and not the eclipse based client.

     

    Glenn