tracker issue : CF-3712824

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

preserveCaseForStructKey should work for query columns too

| View in Tracker

Status/Resolution/Reason: Closed/Withdrawn/Duplicate

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

Created: 02/24/2014

Components: Language

Versions: 11.0

Failure Type: Enhancement Request

Found In Build/Fixed In Build: PublicBeta /

Priority/Frequency: Trivial / Unknown

Locale/System: English / Platforms All

Vote Count: 10

Duplicate ID:	CF-3818767

See http://cfmlblog.adamcameron.me/2014/02/coldfusion-11-query-column-types.html

{quote}
I kinda hoped the this.serialization.preserveCaseForStructKey (see "ColdFusion 11: preserveCaseForStructKey" for commentary on that one) setting might have worked for query columns here too. But... no. I think it should. This perhaps suggests that "preserveCaseForStructKey" needs a rename, too: there are more situations in which case ought to be preserved than simply structs. So let's not tie ourselves down here.
{quote}

-- 
Adam

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

Watson Bug ID:	3712824

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

Attachments:

Comments:

Agreed. (25 character bugger here. 25 character buffer here.)
Vote by External U.
13250 | February 24, 2014 08:54:45 PM GMT
+1 completely agree that queries should be handled as well.
Vote by External U.
13251 | February 24, 2014 09:33:58 PM GMT
Column names in Query metadata always come converted to uppercase. Even if we figure out a way to retain the case, it would be quite risky at this point.
Comment by Awdhesh K.
13238 | February 27, 2014 01:31:00 AM GMT
Can you pls stop closing tickets without an explanation from the developer as to WHY they're closing it! This is quite rude. What's the perceived "design limitation" here? -- Adam
Comment by External U.
13239 | February 27, 2014 01:09:37 PM GMT
Awdhesh, did you just fake a comment here? That comment "Columns names in query..." etc was not there earlier (hence my latter comment). -- Adam
Comment by External U.
13240 | February 28, 2014 07:47:40 AM GMT
Adam, the comment was there but it was not marked external. I just made it external now.
Comment by Rupesh K.
13241 | February 28, 2014 07:51:04 AM GMT
queryName.getMetadata().getColumnLabels() seems to have the correct casing on column names for both SELECT * and SELECT [columns] queries. Is there a reason you don't use that? And why would this be risky? What POSSIBLE risk is there? -- Adam
Comment by External U.
13242 | February 28, 2014 08:02:12 AM GMT
I see. OK, thanks Rupesh. You can remove both my comments referring to that comment and the lack thereof, if you like. Cheers. -- Adam
Comment by External U.
13243 | February 28, 2014 08:03:12 AM GMT
+1 ......................
Vote by External U.
13252 | February 14, 2015 08:33:12 PM GMT
Regarding "it would be quite risky at this point." CF12 is in early stages, so not risky at this point? And I too would like to know: what possible risk? Thanks!, -Aaron
Comment by External U.
13244 | February 15, 2015 02:05:01 PM GMT
+1 query column casing should be preserved.
Vote by External U.
13253 | February 16, 2015 12:25:44 PM GMT
Seconded. What's the risk here?
Comment by External U.
13245 | February 17, 2015 01:40:04 PM GMT
permitting this in the native serialization means less work for me (I'm lazy).
Vote by External U.
13254 | March 19, 2015 01:31:48 PM GMT
+1 ......................
Vote by External U.
13255 | March 19, 2015 01:34:57 PM GMT
This prevents us from being able to use the native serialization when using "this.serialization.serializeQueryAs = 'struct' " alone. Now we must write additional code. *almost* there, come on guys!
Vote by External U.
13256 | March 19, 2015 01:38:43 PM GMT
This creates more work for developers. Sadface.
Vote by External U.
13257 | March 19, 2015 01:40:30 PM GMT
This just adds more work for developers and I'm not sure what the risk would be.
Vote by External U.
13258 | March 19, 2015 01:46:12 PM GMT
Not seeing what's risky abou this. It's also preventing us from using the native serialization in our code, help us out!
Vote by External U.
13259 | March 19, 2015 01:55:10 PM GMT
Hello?
Comment by External U.
13246 | April 15, 2015 03:29:20 AM GMT
Adobe, Can this please be considered for CF12? Thanks!, -Aaron
Comment by External U.
13247 | June 24, 2015 10:25:51 AM GMT
We have added a flag this.serialization.preserverCaseForQueryColumn for this.
Comment by Rupesh K.
13248 | June 24, 2015 11:59:21 AM GMT
Hi Rupesh, I didn't see the "Duplicate ID" till now. Sorry and please disregard! Thanks!, -Aaron
Comment by External U.
13249 | June 24, 2015 01:04:26 PM GMT