[Tickets #8645] Re: Date import broken in turba

[bugs at horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/8645
------------------------------------------------------------------------------
  Ticket             | 8645
  Updated By         | Michael Rubinsky <mrubinsk at horde.org>
  Summary            | Date import broken in turba
  Queue              | Turba
  Version            | 2.3.2
  Type               | Bug
  State              | Assigned
  Priority           | 2. Medium
  Milestone          |
  Patch              |
  Owners             | Michael Rubinsky
------------------------------------------------------------------------------


Michael Rubinsky <mrubinsk at horde.org> (2010-02-13 17:28) wrote:

Trying to solve this -  the date is being stored in the db as 94-2-18  
both in Git and in FW_3, but in Git, Horde_Date is able to handle that  
as input and correctly parse the date. In FW_3, Horde_Date chokes on  
that value as input. If I change the year to 1994 in the original  
file, it gets stored as 1994-2-18, but FW_3 still has trouble with it  
due to the single digit month. I can't find where it is loosing (or  
not receiving) the proper MM format.  I've traced the import process  
all the way from turba to Horde_Data and back again, and all through  
the code the year maintains a YY format, while the month retains a  
single digit format.