This is an automated notification sent by LCG Savannah.
It relates to:
                task #13224, project CDS Invenio

==============================================================================
 LATEST MODIFICATIONS of task #13224:
==============================================================================

Follow-up Comment #1, task #13224 (project cdsware):

As a former sysadmin, I strongly encourage the use of UTC timestamping
everywhere at all times.

Also, Python datetime objects, while a bit expensive, are very clever, and
make timezone conversions (and the production of UTC timestamps from an
arbitrary input string) easy.

==============================================================================
 OVERVIEW of task #13224:
==============================================================================

URL:
  <http://savannah.cern.ch/task/?13224>

                 Summary: Study usage/need of UTC for date/timestamps
                 Project: CDS Invenio
            Submitted by: jcaffaro
            Submitted on: 2010-01-05 07:38
         Should Start On: 2010-01-05 00:00
   Should be Finished on: 2010-01-05 00:00
                Category: BibUpload
                Priority: 1 - Later
                  Status: None
                 Privacy: Public
        Percent Complete: 0%
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any
                  Effort: 0.00

    _______________________________________________________


In general CDS Invenio uses date/timestamps specified in the local timezone
(for eg. for records creation/modification times stored in the DB) without
any special consideration of the Daylight Saving Time offset: this can lead
to ambiguous local times, as the same datestamps (during winter DST switch)
can occur twice a year.

To avoid any confusion (especially with timezone conversions and any
synchronization process relying on dates) one could check the feasibility (or
simply the need) of using Coordinated Universal Time (UTC) as default timezone
for all date/timestamps.

Note that this task would also include checking the behavior of MySQL
regarding date and timezones:
<http://dev.mysql.com/doc/refman/5.1/en/time-zone-support.html>

    _______________________________________________________

Follow-up Comments:


-------------------------------------------------------
Date: 2010-01-08 19:49              By: Joe Blaylock <jblayloc>
As a former sysadmin, I strongly encourage the use of UTC timestamping
everywhere at all times.

Also, Python datetime objects, while a bit expensive, are very clever, and
make timezone conversions (and the production of UTC timestamps from an
arbitrary input string) easy.





    _______________________________________________________

Carbon-Copy List:

CC Address                          | Comment
------------------------------------+-----------------------------
5878                                | -COM-
2407                                | -SUB-




==============================================================================

This item URL is:
  <http://savannah.cern.ch/task/?13224>

_______________________________________________
  Message sent via/by LCG Savannah
  http://savannah.cern.ch/

Reply via email to