minhtu307 / alfresco-business-reporting

Automatically exported from code.google.com/p/alfresco-business-reporting
0 stars 0 forks source link

Incorect date format #24

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. install extension
2. harvest
3. look in database for datetime fields in folder or document tables

What is the expected output? What do you see instead?
I have a file created at 17:30. In database i see 5:30.
So is AM or PM?

What version of the product are you using? On what operating system?
-alfresco-business-reporting v0.8.0.3
-fedora 18 / centos 6.4

Please provide any additional information below.
Standard instalation

Original issue reported on code.google.com by gxg1...@gmail.com on 16 Jun 2013 at 7:56

GoogleCodeExporter commented 8 years ago
Hi gxg1974,

Thanks for trying/using this module, and issueing this ticket.

I have not enough info to work on this issue right now. I expect potential 
timezone issues, and they usually suck.

 * What is your timezone? +9, -7 GMT or standard time?
 * What is the timezone setting of your linux server?
 * Are all your users in the same timezone?
 * What date-field is your problem exactly? 
   * The last modified date the reporting tool adds to a new row? 
   * The cm_created or cm_modified date of Alfresco?
 * is the timestamp of your logfile the issue? 
   * Are all Alfresco and tomcat logfiles affected by this issue?
 * What do you see as a fix?

Cheers!

Original comment by tjarda.p...@incentro.com on 16 Jun 2013 at 11:38

GoogleCodeExporter commented 8 years ago
Hi,

1. My current time, also my time zone on my linux servers are:
Romania Time: Eastern European Time (EET) (GMT + 3)
Europe/Bucharest

2.All user are in  the same timezone.
3. *What date-field is your problem exactly? 

I think all datetime field:
 *Table: document | fields: validFrom, validUntil,cm_created,cm_modified
 *Table: folder | fields: validFrom, validUntil,cm_created,cm_modified
 *Table: site | fields: validFrom, validUntil,cm_created

 example date in db: 2013-05-30 08:44:47.
 example date in alfresco share: Created Date: Joi 30 Mai 2013 20:44:47

 *Table: reportingloginaudit | field timestamp is OK the date format is: 2013-06-13 18:17:37
 Field sys_locale: ro_RO and en_US

None of the logs are affected
 *example entries in log files:
share.log:
15:20:33,281 INFO ...

alfresco.log
14:00:26,453 WARN ...

catalina.out
 2013-06-16 15:20:06,587  INFO ...

 * What do you see as a fix?*
i don't know yet.
i'll investigate the problem and i'll inform you :)

Original comment by gxg1...@gmail.com on 16 Jun 2013 at 12:55

GoogleCodeExporter commented 8 years ago
A fix has been made to make all date fields (related to the reporting tool) 
timezone aware. Next to that, the time definition was in the 0-11hr notation 
instead the 0-23hr, which was a 'clear bug'.
This fix will be released in version 0.8.0.4 soon.

Thanks for issuing the ticket and for working together Geo!

Original comment by tjarda.p...@incentro.com on 16 Jun 2013 at 9:43