tracker issue : CF-4126505

select a category, or use search below
(searches all categories and all time range)
Title:

[ANeff] Bug for: dateTimeFormat(dateTime, "iso") truncates milliseconds

| View in Tracker

Status/Resolution/Reason: Closed/Won't Fix/

Reporter/Name(from Bugbase): Aaron Neff / Aaron Neff (Aaron Neff)

Created: 03/09/2016

Components: Language

Versions: 2016

Failure Type: Unspecified

Found In Build/Fixed In Build: Beta1_v12 /

Priority/Frequency: Trivial / Unknown

Locale/System: English / Win All

Vote Count: 2

dateTimeFormat(dateTime, "iso") truncates milliseconds

Repro:

<cfscript>
  dateTime = createDateTime(2016,1,3,1,2,3);
  dateTime = dateAdd("l", 123, dateTime);
  writeOutput(dateTimeFormat(dateTime, "iso"));
</cfscript>

Actual result: 2016-01-03T01:02:03Z

Expected result: 2016-01-03T01:02:03.123Z

<cfscript>
  dateTime = createDateTime(2016,1,3,1,2,3);
  writeOutput(dateTimeFormat(dateTime, "iso"));
</cfscript>

Actual result: 2016-01-03T01:02:03Z

Expected result: 2016-01-03T01:02:03.000Z

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	4126505

External Customer Info:
External Company:  
External Customer Name: Aaron Neff
External Customer Email: adobelabs@itisdesign.com
External Test Config:

Attachments:

Comments:

Adding BUG AUDIT TRAIL ********action: updated fieldName: Reason newValue: Blank oldValue: NotABug oprid: vmannebo recordName: RQ_DEFECT timpestamp: 2015-12-22 03:54:41.0 action: updated fieldName: Status newValue: NeverFix oldValue: ToTest oprid: vmannebo recordName: RQ_DEFECT timpestamp: 2015-12-22 03:54:41.0 action: updated fieldName: State newValue: Closed oldValue: Open oprid: vmannebo recordName: RQ_DEFECT timpestamp: 2015-12-22 03:54:41.0 action: updated fieldName: Owner newValue: Blank oldValue: inoel oprid: vmannebo recordName: RQ_DEFECT timpestamp: 2015-12-22 03:54:41.0 action: updated fieldName: Closed By newValue: vmannebo oldValue: Blank oprid: vmannebo recordName: RQ_DEFECT timpestamp: 2015-12-22 03:54:41.0 action: updated fieldName: Date Closed newValue: 2015-12-21 19:54:41.0 oldValue: Blank oprid: vmannebo recordName: RQ_DEFECT timpestamp: 2015-12-22 03:54:41.0 action: updated fieldName: Reason newValue: NotABug oldValue: Blank oprid: siddhart recordName: RQ_DEFECT timpestamp: 2015-12-21 11:27:57.0 action: updated fieldName: Status newValue: ToTest oldValue: ToFix oprid: siddhart recordName: RQ_DEFECT timpestamp: 2015-12-21 11:27:57.0 action: updated fieldName: Owner newValue: inoel oldValue: siddhart oprid: siddhart recordName: RQ_DEFECT timpestamp: 2015-12-21 11:27:57.0 action: updated fieldName: Fix By Milestone newValue: Gold Master oldValue: Blank oprid: inoel recordName: RQ_DEFECT timpestamp: 2015-12-14 10:11:03.0 action: updated fieldName: Dev Assigned newValue: siddhart oldValue: awdhesh oprid: inoel recordName: RQ_DEFECT timpestamp: 2015-12-14 10:11:03.0 action: updated fieldName: Status newValue: ToFix oldValue: Unverified oprid: inoel recordName: RQ_DEFECT timpestamp: 2015-12-14 10:11:03.0 action: updated fieldName: Fix By Product Milestone newValue: Gold Master oldValue: Blank oprid: inoel recordName: RQ_DEFECT timpestamp: 2015-12-14 10:11:03.0 action: updated fieldName: Reason newValue: Blank oldValue: Blank oprid: inoel recordName: RQ_DEFECT timpestamp: 2015-12-14 10:11:03.0 action: updated fieldName: Owner newValue: siddhart oldValue: inoel oprid: inoel recordName: RQ_DEFECT timpestamp: 2015-12-14 10:11:03.0
Comment by CFwatson U.
3935 | March 09, 2016 02:21:58 AM GMT
Added By: PreRelease User User Name:Aaron Neff Note Added: Please implement correctly and do not keep the language hamstrung to the past. Date Added :2016-02-10 13:36:18.0 Added By: PreRelease User User Name:Aaron Neff Note Added: Hello?? Date Added :2016-02-10 13:35:38.0 Added By: PreRelease User User Name:Aaron Neff Note Added: Hi Adobe, The primary use case for dateTimeFormat("iso") is to publish date/time via APIs. For APIs, date/time should be as accurate as possible. It should not matter if existing dateTimeFormat() masks "medium"/"long"/"full" use seconds as the smallest unit. Those masks serve a different purpose and would not be used in CF APIs. APIs often return timestamps in full ISO format w/ milliseconds. Example: eBay returns YYYY-MM-DDTHH:MM:SS.SSSZ (please see "datetime" here: http://developer.ebay.com/devzone/finding/callref/types/simpleTypes.html). Also, CF-3429713 would make milliseconds the smallest unit everywhere. Could you please reconsider? Could you please discuss again w/ Rupesh? Thanks!, -Aaron Date Added :2016-01-22 09:56:22.0 Added By: PreRelease User User Name:Aaron Neff Note Added: Please see my earlier comment: The forum thread discussing this ticket is: http://prerelease.adobe.com/r/?56bbf8fbaecd4c739ef47cdb966b51e7 And millisecond() is being considered per CF-3429713 so this should be re-opened. Date Added :2016-01-09 01:06:46.0 Added By:siddhart Note Added: Since everywhere we are using seconds as the smallest unit, adding milliseconds here will not be consistent. (Discussed with Rupesh) Date Added :2015-12-21 11:27:57.0 Added By: PreRelease User User Name:Aaron Neff Note Added: The forum thread discussing this ticket is: http://prerelease.adobe.com/r/?56bbf8fbaecd4c739ef47cdb966b51e7 Please follow-up in that thread, not here in this ticket. Date Added :2015-12-12 05:15:12.0 Added By: PreRelease User User Name:Aaron Neff Note Added: Entered Bug. Date Added :2015-12-11 09:44:16.0
Comment by CFwatson U.
3936 | March 09, 2016 02:21:59 AM GMT