tracker issue : CF-3636794

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

QoQ CAST() bug

| View in Tracker

Status/Resolution/Reason: Closed/Fixed/

Reporter/Name(from Bugbase): Adam Cameron / Adam Cameron (Adam Cameron)

Created: 09/20/2013

Components: Database, Query-of-Query(IMQ)

Versions: 10.0

Failure Type:

Found In Build/Fixed In Build: Final /

Priority/Frequency: Major / Some users will encounter

Locale/System: English / Win All

Vote Count: 0

See: http://cfmlblog.adamcameron.me/2013/09/expectations-management-date-casting-in.html

Summary: casting to DATE, TIME do not do what they imply they do: they both simply return a full date/time.

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

Watson Bug ID:	3636794

Deployment Phase:	Release Candidate

External Customer Info:
External Company:  
External Customer Name: Adam Cameron.
External Customer Email:  
External Test Config: My Hardware and Environment details:

Attachments:

Comments:

Issue related to time has been fixed and will be available in the next release. However, Issue related to date has still not been fixed because of too many changes, so I have logged a tracking bug#CF-3688938 for it.
Comment by Nimit S.
14485 | January 03, 2014 08:43:07 AM GMT
So to be clear: casting to TIME will result in the value having just a time component; but the DATE one will still return a DATE/TIME because of backwards compat concerns? If so: yeah, makes sense. Cheers. -- Adam
Comment by External U.
14486 | January 03, 2014 09:17:14 AM GMT
Yes, casting to Time will result in the time component only.
Comment by Nimit S.
14487 | January 03, 2014 09:21:36 AM GMT