Weird behaviour with DATETOSTRING_LOCAL in DQL statements
Hi,
I am experiencing weird behaviour with the DATETOSTRING_LOCAL
function in DQL while trying to group objects based on day.
It behaves identically to the normal DATETOSTRING
function unless when it is used in a subquery.
(The real life queries are more complicated than the examples below to illustrate the issue.)
Example 1: normal usage - no issues here
Example 2: the normal DATETOSTRING
method behaving as it should
You see the subquery returns the dates correctly as a string in a short format YYYY-MM-dd and the main query can group on it.
Example 3: the localised DATETOSTRING_LOCAL
method behaving differently (incorrectly) while using the same query as Example 2
It doesn't format correctly.
Does anybody know why? Is this a bug or an expected, albeit weird, result?
Categories
- All Categories
- 108 Developer Announcements
- 53 Articles
- 106 General Questions
- 144 IM Services
- 43 OpenText Hackathon
- 32 Developer Tools
- 20.6K Analytics
- 4.1K AppWorks
- 8.9K Extended ECM
- 899 Cloud Fax and Notifications
- 77 Digital Asset Management
- 9.3K Documentum
- 29 eDOCS
- 120 Exstream
- 39.8K TeamSite
- 1.7K Web Experience Management