I am not a regular user of these community forums, and I clearly made a few mistakes in my post:
- The key topic wasn't clear - my main issue is with the QueryExecute param evaluation throwing an error when quotes are not used around the maxlength parameter;
- I had been assuming the issue was happening with Java 9.0.4 as well, but hadn't actually checked that (although it does still happen on the default Java 9.0.4 btw);
- I should not have mentioned Java 10, knowing that it was not officially supported;
- I didn't consider the broader community interpretation of my post, I was just flagging an issue I encountered for Adobe to investigate pre official release of CF2018;
My post to Adobe re Java 9/10/11 was just on the CF2018 pre-release blog post (you can see it *currently* at the end of the thread), and no they did not reply:
Public beta for Adobe ColdFusion (2018 release) and Adobe ColdFusion Builder (2018 release) | ColdFusion
In that context, I don't think the question is answered, because the issue still exists in the CF2018 Public Beta with Updater 1 applied.
Here is a code sample that can reproduce the issue:
<cfscript>
qMyQuery = QueryExecute(" SELECT Test = :TestValue ", {TestValue = { cfsqltype="CF_SQL_CHAR", maxlength=64, value="Some text" }, { Datasource = "DataSource", Username = "UserName", Password = "Password" } );
WriteDump(qMyQuery);
</cfscript>
I would like Adobe to look into this, or alternatively advise if quotes are now required in that context (they were not previously). Should I be posting issues that I have in the CF2018 Pre Release to another location rather than the Community Forums?
@Benjamin Reid
Thanks for reporting this . We figured out this is a regression caused due to changes made for data type preservation in CF 2018 and we have now fixed this . Regarding the official support for Java 10 for CF 2018 , the current plan is to support it even though we have shipped the installers with Java 9 JRE .. we are contemplating on switching to Java 10 .
BTW , even the Public beta build was certified in Java 10 before release so you are safe to continue to test with Java 10