Title:
Bug 87092:CF's parseDateTime does not understand float values generated by interaction with timespans (e
| View in TrackerStatus/Resolution/Reason: Closed/Withdrawn/
Reporter/Name(from Bugbase): Michael Zock / Michael Zock (MikeZ83)
Created: 09/11/2011
Components: Legacy Area, Usability
Versions: 9.0
Failure Type: Unspecified
Found In Build/Fixed In Build: 9.0.1.274733 /
Priority/Frequency: Trivial / Unknown
Locale/System: English / Platforms All
Vote Count: 2
Problem:
CF's parseDateTime does not understand float values generated by interaction with timespans (e.g. #parseDateTime(now()+createTimeSpan(0,2,30,0))#). The conversion only works if you're using createOdbcDateTime() instead of parseDateTime().
Method:
#parseDateTime(now()+createTimeSpan(0,2,30,0))# <!-- This won't work --->#createOdbcDateTime(now()+createTimeSpan(0,2,30,0))# <!-- This will work --->
Result:
CF's parseDateTime does not parse float values generated by interaction with timespans (e.g. #parseDateTime(now()+createTimeSpan(0,2,30,0))#). The conversion only works if you're use createOdbcDate() instead of parseDateTime().
----------------------------- Additional Watson Details -----------------------------
Watson Bug ID: 3044017
External Customer Info:
External Company:
External Customer Name: Michael Zock
External Customer Email: 44555C93470B2F2F992015A9
External Test Config: 09/11/2011Attachments:
Comments: