Project:
| View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||
| ID | ||||||||
| 0030508 | ||||||||
| Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||
| defect | [Openbravo ERP] A. Platform | major | always | 2015-08-06 13:45 | 2015-08-12 11:36 | |||
| Reporter | Orekaria | View Status | public | |||||
| Assigned To | platform | |||||||
| Priority | urgent | Resolution | invalid | Fixed in Version | ||||
| Status | closed | Fix in branch | Fixed in SCM revision | |||||
| Projection | none | ETA | none | Target Version | ||||
| OS | Any | Database | Any | Java version | ||||
| OS Version | Database version | Ant version | ||||||
| Product Version | SCM revision | |||||||
| Review Assigned To | ||||||||
| Web browser | ||||||||
| Modules | Core | |||||||
| Regression level | ||||||||
| Regression date | ||||||||
| Regression introduced in release | ||||||||
| Regression introduced by commit | ||||||||
| Triggers an Emergency Pack | No | |||||||
| Summary | 0030508: Date fields do not sort by milliseconds when using the local cache | |||||||
| Description | Date 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 Reproduce | This 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) | |||||||
| Tags | No tags attached. | |||||||
| Attached Files | ||||||||
 Relationships [ Relation Graph ]
[ Dependency Graph ]
|
|||||||||
|
|||||||||
 Relationships |
|
Notes |
|
|
(0079320) alostale (manager) 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 [^] |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2015-08-06 13:45 | Orekaria | New Issue | |
| 2015-08-06 13:45 | Orekaria | Assigned To | => platform |
| 2015-08-06 13:45 | Orekaria | Modules | => Core |
| 2015-08-06 13:45 | Orekaria | Triggers an Emergency Pack | => No |
| 2015-08-06 14:16 | Orekaria | Steps to Reproduce Updated | View Revisions |
| 2015-08-06 14:16 | Orekaria | Steps to Reproduce Updated | View Revisions |
| 2015-08-06 14:18 | Orekaria | Summary | LogClient 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:18 | Orekaria | Description Updated | View Revisions |
| 2015-08-12 11:36 | alostale | Note Added: 0079320 | |
| 2015-08-12 11:36 | alostale | Status | new => closed |
| 2015-08-12 11:36 | alostale | Resolution | open => invalid |
| 2015-08-12 12:32 | guilleaer | Relationship added | blocks 0030558 |
|
Issue History |
| Copyright © 2000 - 2009 MantisBT Group |
 |