tracker issue : CF-3713323

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

Iterator methods on query objects have not been implemented

| View in Tracker

Status/Resolution/Reason: Closed/Fixed/

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

Created: 02/25/2014

Components: Language

Versions: 11.0

Failure Type: Enhancement Request

Found In Build/Fixed In Build: PublicBeta / 294433

Priority/Frequency: Normal / Unknown

Locale/System: English / Platforms All

Vote Count: 13

Listed in the version 2016.0.0.297996 Issues Fixed doc
Verification notes: verified_fixed on August 25, 2019 using build 2016.0.01.298513
There should be each(), filter(), map(), reduce() methods on query objects as well (as per arrays, structs, lists)


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

Watson Bug ID:	3713323


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



This would be a nice addition but too late in the game.
Comment by Rupesh K.
13185 | March 03, 2014 09:16:14 AM GMT
It's not really "an addition" it's what you should have done from the outset. But so be it. -- Adam
Comment by External U.
13186 | March 03, 2014 09:36:27 AM GMT
Queries are such an idiomatic part of CFML (the ORIGINAL data structure of the language) this should be a no-brainer.
Vote by External U.
13198 | March 11, 2014 04:09:02 PM GMT
I'm really surprised this was missed. As Nathan said, queries are an integral part of CF and each should be supported.
Vote by External U.
13199 | November 20, 2014 04:14:43 PM GMT
Expectations. If iterator methods are implemented on one thing, it should have been implemented on everything. :|
Vote by External U.
13200 | November 20, 2014 04:27:34 PM GMT
Please explain in 25 characters or more how this feature impacts productivity and why you are adding a vot
Vote by External U.
13201 | November 20, 2014 04:40:08 PM GMT
obviously should have been in the first place
Vote by External U.
13202 | November 20, 2014 04:46:19 PM GMT
Vote must be between 25 and 4000 characters
Vote by External U.
13203 | November 20, 2014 05:02:28 PM GMT
I'd be keen if you could have the courtesy to respond to one of your clients, Rupesh.
Comment by External U.
13187 | November 20, 2014 05:34:36 PM GMT
It's common sense to have these methods available.
Vote by External U.
13204 | November 20, 2014 05:37:55 PM GMT
+1 ... Dramatically e-enable backward-compatible interfaces with fully tested materials. Interactively procrastinate orthogonal intellectual capital after revolutionary processes. Efficiently plagiarize one-to-one human capital without plug-and-play portals. Distinctively morph dynamic manufactured.
Vote by External U.
13205 | November 20, 2014 05:40:53 PM GMT
Ray asked me to vote for this, so here I am.
Vote by External U.
13206 | November 20, 2014 06:13:47 PM GMT
+1 I think queries are possibly the first place iterator functions should have been added to the language.
Vote by External U.
13207 | November 20, 2014 11:27:15 PM GMT
If I may ask - respond to which question, Adam?
Comment by Rupesh K.
13188 | November 21, 2014 12:42:42 AM GMT
That, Rupesh, is a very good question. I'm buggered if I know ;-) I think I probably had more than one ticket open at once in my browser, and put this comment against the wrong one. I wonder what the other one was? Are there any other tickets in which I've got the most recent comment, it's asking a question, and you haven't answered it?
Comment by External U.
13189 | November 21, 2014 03:58:06 AM GMT
That would be very difficult to find given the number of bugs you have commented on ;-)
Comment by Rupesh K.
13190 | November 21, 2014 07:09:58 AM GMT
You provide me with such a wealth of material, Rupesh ;-)
Comment by External U.
13191 | November 21, 2014 06:55:02 PM GMT
queries are something I work with everyday. Adding these methods would be immediately useful.
Vote by External U.
13208 | November 21, 2014 07:08:34 PM GMT
Added support for each and filter. Will evaluate and add support for map,reduce. A tracking bug:CF-3863003 logged for the same.
Comment by Awdhesh K.
13192 | December 05, 2014 06:32:32 AM GMT
Oh, and there should also be a sort method too. Again, for parity with the other collections' iteration methods. All collection types should have the same "Iterable" interface, really (obviously not an *actual* interface, as the method signatures vary from type to type, but you perhaps get what I mean.
Comment by External U.
13193 | December 05, 2014 06:37:00 AM GMT
The scope of this bug is limited to inclusion of each() and filter() methods for query objects. Support for map, reduce and sort will be addressed in bug CF-3863003.
Comment by Immanuel N.
13194 | June 19, 2015 01:07:37 AM GMT
Hi Immanuel, thanks for that. What's the release schedule for this?
Comment by External U.
13195 | July 12, 2015 10:06:01 AM GMT
+1 ......................
Vote by External U.
13209 | September 26, 2015 11:10:38 PM GMT
Vote by External U.
13210 | October 15, 2015 09:18:56 AM GMT
we have already added the support for each and filter for query. We are keeping this bug open for map and reduce functions for query.
Comment by Rupesh K.
13196 | October 16, 2015 07:24:58 AM GMT
This fix addresses support for query.each() and query.filter(). map() and reduce() will be addressed as part of fix for bug #CF-3863003.
Comment by Immanuel N.
13197 | November 09, 2015 09:39:26 PM GMT
Hi Adobe, I've verified this is fixed in CF2016 Update 1 (build 2016.0.01.298513), for .each() and .filter(). Thanks!, -Aaron
Comment by Aaron N.
31208 | August 25, 2019 07:58:03 PM GMT