Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0030508Openbravo ERPA. Platformpublic2015-08-06 13:452015-08-12 11:36
ReporterOrekaria 
Assigned Toplatform 
PriorityurgentSeveritymajorReproducibilityalways
StatusclosedResolutioninvalid 
PlatformOS5OS Version
Product Version 
Target VersionFixed in Version 
Merge Request Status
Review Assigned To
OBNetwork customer
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0030508: Date fields do not sort by milliseconds when using the local cache
DescriptionDate fields do not sort by milliseconds when using the local cache

We detected this issue in Retail, in which the order of the messages in the log are crucial to analyse asynchronous processes
Steps To ReproduceThis issue can be reproduced in any grid with a date field

Most probably the easiest way to see the issue is verifying that dates are locally stored removing the milliseconds, so there is no way for the local cache to recreate the correct order


e.g:

With Retail In the ERP
Open the LogClient window

1)
Order by Creation Date
Verify the order of the some of the messages when there are in the same second

2)
Create a filter so there are less than 100 records
Sort by Creation Date
Verify that the order of the messages has changed when the messages are in the same second (INCORRECT)
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
blocks feature request 0030558 new Retail Retail Modules Log client messages should show a specific time when it was generated 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2015-08-06 13:45OrekariaNew Issue
2015-08-06 13:45OrekariaAssigned To => platform
2015-08-06 13:45OrekariaModules => Core
2015-08-06 13:45OrekariaTriggers an Emergency Pack => No
2015-08-06 14:16OrekariaSteps to Reproduce Updatedbug_revision_view_page.php?rev_id=9163#r9163
2015-08-06 14:16OrekariaSteps to Reproduce Updatedbug_revision_view_page.php?rev_id=9164#r9164
2015-08-06 14:18OrekariaSummaryLogClient does not sort by milliseconds when its using the local cache => Date fields do not sort by milliseconds when using the local cache
2015-08-06 14:18OrekariaDescription Updatedbug_revision_view_page.php?rev_id=9166#r9166
2015-08-12 11:36alostaleNote Added: 0079320
2015-08-12 11:36alostaleStatusnew => closed
2015-08-12 11:36alostaleResolutionopen => invalid
2015-08-12 12:32guilleaerRelationship addedblocks 0030558

Notes
(0079320)
alostale   
2015-08-12 11:36   
Date Time columns are backed up in DB:
* PostgreSQL: TIMESTAMP with a resolution up to microsecond [1]
* Oracle: DATE type column with a resolution up to seconds [2]

This is one the reasons it is not possible to make this reference work cross DB to sort by milliseconds.

If this is required, a different reference should be used/created.

[1] http://www.postgresql.org/docs/9.4/static/datatype-datetime.html [^]
[2] http://docs.oracle.com/cd/B28359_01/server.111/b28318/datatype.htm#i1847 [^]