tracker issue : CF-4098395

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

isnull with argument struct["key"] will cause a element is undefined error

| View in Tracker

Status/Resolution/Reason: Closed/Fixed/Fixed

Reporter/Name(from Bugbase): Jork Zijlstra / Jork Zijlstra (Jork Zijlstra)

Created: 12/10/2015

Components: Core Runtime

Versions: 2016,11.0,10.0

Failure Type:

Found In Build/Fixed In Build: Final / 2018,0,0,308372

Priority/Frequency: Normal / All users will encounter

Locale/System: English / Linux All

Vote Count: 4

Problem Description:
Calling a isnull(struct["key"])); with a struct notation like struct["key"] (square bracket version) will cause an element us undefined in struct error.

Steps to Reproduce:
	
{code:java}
struct = {"key" = javacast("null", 0)};
writeDump(isnull(struct["key"]));
{code}


Actual Result:
Element key is undefined in a CFML structure referenced as part of an expression. 

Expected Result:
Result off the isnull method

Any Workarounds:
Do not use the ["key"] (square brackets) notation to navigate the struct
Use the dot notation like isnull(struct.key);

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

Watson Bug ID:	4098395

External Customer Info:
External Company:  
External Customer Name: Jork Zijlstra
External Customer Email:  
External Test Config: My Hardware and Environment details:

Ubuntu 14.04, CF10,0,18,29633

Attachments:

Comments:

+1, there shouldn't be this discrepancy
Vote by External U.
5118 | December 10, 2015 05:21:04 AM GMT
Bit late for CF12. Will take it up for next version.
Comment by Awdhesh K.
5114 | December 18, 2015 02:01:41 AM GMT
Thnx for the info. So it won't be fixed in CF10, CF11 and CF12 but in ...?
Comment by External U.
5115 | December 18, 2015 02:50:25 AM GMT
+1 ......................
Vote by External U.
5119 | January 05, 2016 03:06:04 AM GMT
I would expect it to be fixed in CF10 update 19, CF 11 update 8 and CF12 update 1, right?
Comment by External U.
5116 | January 05, 2016 04:49:57 AM GMT
Is this a duplicate of https://tracker.adobe.com/#/view/CF-3777274 ?
Comment by Bradley W.
5117 | April 03, 2017 01:34:36 AM GMT
Yup. Adobe, why is this issue still hanging around after almost four years ince it was first reported?
Comment by Adam C.
27298 | April 05, 2018 07:44:19 AM GMT
Please also confirm it'll be fixed in all supported versions of CF.
Comment by Adam C.
27299 | April 05, 2018 07:44:55 AM GMT
This bug is not fixed in the latest version of ACF2016.
Comment by Samuel K.
33121 | February 14, 2020 02:01:51 AM GMT