Issue (View Online)

Key: NXP-1410
Issue Type: Bug Bug
Status: Open Open
Priority: Minor Minor
Assignee: Thierry Delprat
Reporter: Georges Racinet

Operations

View all
View comments
View history
Inconsistence of time locale for date only fields 
Updated: 08/08/07 20:27   Created: 03/08/07 10:43  

The following issue has been updated.

Updater: Georges Racinet
Date: 08/08/07 20:27
Comment:
patch for nuxeo-platform-compass-plugin to apply once platform is on the newer core version

Field Original Value New Value
Change By Georges Racinet on 08/08/07 20:27
Attachment patch

Project: Nuxeo Enterprise Platform 5
Attachments: patch

 Description   
Here I mean fields that are used to store a pure date information, without time.
The symptom is that range queries on these fields seem to miss the first day: if user entered 2007/01/01 on doc 'foo' and one searches for values from 2007/01/01, 'foo' won't be returned.

The reason is that the search service transforms the date into this timestamp: 2007-01-01 00:00 (GMT +2) whereas the application had stored 2007-01-01 00:00 (no timezone).

Needs to be investigated further to be sure where to attack.

This message was automatically generated by Atlassian JIRA Enterprise Edition, Version: 3.10-260 - Bug/feature request.
If you think it was sent incorrectly, contact one of this server's administrators.

_______________________________________________
ECM-tickets mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm-tickets

Reply via email to