Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Issue Details[ Jump to Notes ] [ Issue History ] [ Print ]
ID
0010507
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[Openbravo ERP] 01. General setupmajorsometimes2009-09-07 20:452009-09-13 19:31
ReporternetworkbView Statuspublic 
Assigned Toiperdomo 
PriorityurgentResolutionno change requiredFixed in Version
StatusclosedFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version2.50MP6
OSAnyDatabasePostgreSQLJava version
OS VersionDatabase versionAnt version
Product Version2.50MP1SCM revision 
Merge Request Status
Review Assigned To
OBNetwork customerOBPS
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0010507: Date parse error when scheduling process

DescriptionWorking with US date format ('MM-DD-YYYY' in Openbravo.properties) when schedule a process an error occurs parsing date format. The system is trying to convert start date from format DD-MM-YYYY to MM-DD-YYYY.

It happens because the database is configured as european and "select date" queries obtain dates in european format, but the parser (in java) is configured as US format. When select method of src/org/openbravo/scheduling/trigger_data.xsql is executed the start date obtained is (DD-MM-YYYY).
Steps To Reproduce- Configure Openbravo Properties as mm-dd-yyyy
- Go to General Setup || Application || Process Scheduling || Process Scheduling
- Schedule one process
- Press button Schedule.
Proposed SolutionIn src/org/openbravo/scheduling/OBScheduler.java in line 347

final TriggerData data = TriggerData.select(conn, name); add new parameter in query : dateTimeFormat.

Add new parameter in xsql
In src/org/openbravo/scheduling/trigger_data.xsql modifye the method:

select .....TO_CHAR(STARTDATA,?)

where ? is dateTimeFormat.
TagsNo tags attached.
Attached Filespng file icon schedule1.png [^] (72,448 bytes) 2009-09-13 19:13


png file icon schedule2.png [^] (27,068 bytes) 2009-09-13 19:13

- Relationships [ Relation Graph ] [ Dependency Graph ]
duplicate of defect 0009202 closediperdomo ProcessRunData has the date format hardcoded 

-  Notes
(0019494)
iperdomo (viewer)
2009-09-08 07:19

 I tested using US date format, dd-mm-yyyy and I was able to schedule a process. This is fixed since 2.50MP2.

Cheers,

Iván
(0019834)
networkb (viewer)
2009-09-11 21:45

 This is not the same issue than 0009202. The bug fix of 0009202 was applied and kept giving the error.

When we applied the proposed solution, the error was solved. So please, can you reconsider this issue?

Thank you.
(0019865)
iperdomo (viewer)
2009-09-13 19:30

 Hi,

Probably true that is not the same problem, but I'm able to schedule a process using US date format (mm-dd-yyy). Attached you'll find the process request (schedule1.png) and the process execution (schedule2.png).

If you want to use US date format, you must change the Openbravo.properties:
####################
# Date/time format #
####################

dateFormat.js=%m-%d-%Y
dateFormat.sql=MM-DD-YYYY
dateFormat.java=MM-dd-yyyy
dateTimeFormat.java=MM-dd-yyyy HH:mm:ss

But also the bbdd.sessionConfig:

When using PostgreSQL:
bbdd.sessionConfig=select update_dateFormat('MM-DD-YYYY')

When using Oracle:
bbdd.sessionConfig=ALTER SESSION SET NLS_DATE_FORMAT='MM-DD-YYYY' NLS_NUMERIC_CHARACTERS='.,'

After changing the Openbravo.properties, and assuming that you have the application compiled, you *must* execute ant compile.complete. This step is required because SqlC uses the dateFormat.java dateTimeFormat.java properties when generating the Data class.

In the TriggerData case, you have to lines like this ones:
objectTriggerData.startDate = UtilSql.getDateValue(result, "start_date", "MM-dd-yyyy");
objectTriggerData.finishesDate = UtilSql.getDateValue(result, "finishes_date", "MM-dd-yyyy");

The part "MM-dd-yyyy" is using the dateFormat.java property.

There is no need to pass the dateTime to trigger_data.xsql, what happened is that because you changed the _data.xsql when you compiled this class got regenerated and therefore the new dateFormat was used.

The to_char() call is extracting the hours:minutes:seconds and there is no need to pass the datetime format. e.g.

SELECT TO_CHAR(Start_Time, 'HH24:MI:SS') AS Start_Time, Start_Date, TO_CHAR(Finishes_Time, 'HH24:MI:SS') AS Finishes_Time, Finishes_Date FROM AD_Process_Request ORDER BY Created DESC LIMIT 1;

 start_time | start_date | finishes_time | finishes_date
------------+---------------------+---------------+---------------
 19:08:00 | 2009-09-13 00:00:00 | |


So the start_time is calculated correctly.

- Issue History
Date Modified Username Field Change
2009-09-07 20:45 networkb New Issue
2009-09-07 20:45 networkb Assigned To => rafaroda
2009-09-07 20:45 networkb OBNetwork customer => Yes
2009-09-08 07:17 iperdomo Assigned To rafaroda => iperdomo
2009-09-08 07:19 iperdomo Relationship added duplicate of 0009202
2009-09-08 07:19 iperdomo Status new => closed
2009-09-08 07:19 iperdomo Note Added: 0019494
2009-09-08 07:19 iperdomo Duplicate ID 0 => 9202
2009-09-08 07:19 iperdomo Resolution open => duplicate
2009-09-09 00:00 anonymous sf_bug_id 0 => 2854709
2009-09-11 21:45 networkb Status closed => new
2009-09-11 21:45 networkb Resolution duplicate => open
2009-09-11 21:45 networkb Note Added: 0019834
2009-09-11 21:47 networkb Target Version 2.50MP1 => 2.50MP6
2009-09-12 06:42 rafaroda Priority immediate => urgent
2009-09-12 06:42 rafaroda Status new => scheduled
2009-09-13 19:13 iperdomo File Added: schedule1.png
2009-09-13 19:13 iperdomo File Added: schedule2.png
2009-09-13 19:30 iperdomo Note Added: 0019865
2009-09-13 19:31 iperdomo Status scheduled => closed
2009-09-13 19:31 iperdomo Duplicate ID 9202 => 0
2009-09-13 19:31 iperdomo Resolution open => no change required

Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker