preserveCaseForQueryColumn no longer working?

kpetrow · September 16, 2024, 6:48pm

I Set this in my application.cfc but it is no longer wokring after updating to 6.x

<cfset this.serialization.preserveCaseForQueryColumn = false>
<cfset this.sessionManagement = true >
<cfset this.setclientcookies = true >

Don’t forget to tell us about your stack!

OS: windows
Java Version: java 17.0.12 2024-07-16 LTS
Tomcat Version: Apache Tomcat 9.0
Lucee Version: preserveCaseForQueryColumn

kpetrow · September 24, 2024, 8:35pm

Is there a specific place for 6.0 bugs?

andreas · October 1, 2024, 3:08am

When placing a bug at Jira, you’ll be asked to add the affected version. That is the place where to file the bug.

srstsavage · April 16, 2025, 5:56pm

Hitting this as well, created a Jira ticket:

https://luceeserver.atlassian.net/browse/LDEV-5518

Zackster · April 16, 2025, 6:37pm

mmmm, we have test coverage, but for via Application.cfc

github.com

lucee/Lucee/blob/6.2/test/general/SerializeJSON.cfc#L80


      
          					 "id"          : 1
          					,"Name"        : "POTHYS"
          					,"designation" : "Associate Software Engineer"
          				};
          
          				var jsonObject = serializeJSON( mystruct );
          				expect(find("NAME", jsonObject)).toBeGT(0);
          				expect(find("ID", jsonObject)).toBeGT(0);
          			});
          
          			it(title="Checking serializeJSON() with preserveCaseForQueryColumn is true", body=function(){
          				var serSettings =  getApplicationSettings().serialization;
          				serSettings.serializeQueryAs = "row";
          				serSettings.preserveCaseForQueryColumn = true;
          				application action="update"	SerializationSettings=serSettings;
          
          				var data = queryNew("ID, DateJoined", "INTEGER, TIMESTAMP", [{ID=1, DateJoined="2017-01-03 10:57:54"}, {ID=2, DateJoined="2017-01-03 10:57:54"}, {ID=3, DateJoined="2017-01-03 10:57:54"}]);
          				var jsonObject = serializeJSON( data );
          				expect(find("DateJoined", jsonObject)).toBeGT(0);
          				expect(find("ID", jsonObject)).toBeGT(0);
          			});

I’m on it

Zackster · April 16, 2025, 7:23pm

for now this.serialization works, it was missing the alias

srstsavage · April 17, 2025, 12:57am

docker-compose.yml (1.8 KB)

Thanks for taking a look at this! As I’m already using this.serialization.preserveCaseForQueryColumn = false; in Application.cfc, I suspect my issue has something specficially to do with the way that the columns are serialized when a query is returned as json in a cfcomponent method invocation.

I’ve attached here a docker-compose.yml file that reproduces the issue (loads the same Application.cfc and Test.cfc components into a Lucee 5 and Lucee 6 image so you can see the difference in serialization).

➜  LDEV-5518-REPRO docker compose up -d
[+] Running 3/3
 ✔ Network ldev-5518-repro_default     Created                                                                                                                                           0.1s 
 ✔ Container ldev-5518-repro-lucee5-1  Started                                                                                                                                           0.5s 
 ✔ Container ldev-5518-repro-lucee6-1  Started                                                                                                                                           0.5s 
➜  LDEV-5518-REPRO curl "http://localhost:7005/Test.cfc?method=test"
{"COLUMNS":["ID","NAME"],"DATA":[[1,"Neo"],[2,"Trinity"],[3,"Morpheus"]]}%
➜  LDEV-5518-REPRO curl "http://localhost:7006/Test.cfc?method=test"
{"COLUMNS":["iD","NaMe"],"DATA":[[1,"Neo"],[2,"Trinity"],[3,"Morpheus"]]}%

Zackster · April 17, 2025, 9:45am

single docker file repo, nice!!!

the regression was introduced with 6.0.0.406

https://luceeserver.atlassian.net/browse/LDEV-5518?focusedCommentId=60183

srstsavage · April 17, 2025, 3:24pm

single docker file repo, nice!!!

Glad someone else thinks that’s cool!

Thanks again for looking into this, hopefully an easy fix now that the issue is identified.