Attribute type should be appropriately formatted
Reported by Ben Hood | April 8th, 2011 @ 03:47 PM | in 0.9.3
#199 fixed an issue where the DateCategoryFunction could not parse a yyyy-MM-dd date. However, the side effect of this is that when the agent generates subsequent constraints for further querying, it does so using the date type, which, in turn uses the default serialization of that class, i.e. a string with a complete ISO date including seconds and timezone. When this is sent back to the participant, it is legitimately expecting a date string in the format it sent originally sent out.
Hence we need a mechanism that honours the formatting/implicit type that the participant understands - this should probably be configurable together with the data type of the category.
Comments and changes to this ticket
-
Ben Hood April 19th, 2011 @ 07:49 PM
- State changed from “new” to “duplicate”
This problem has been addressed as part of #204, hence closing this issue.
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
A Real Time Differencing Tool.
Ben Hood