Lucee 6 comes with cfqueryparam change that empty values are not valid for numbers anymore. Previously if "" is passed to cfqueryparam, I think it was silently converted to null, and then went to DB. It was working fine together with idea that everything is a string, since HTTP request is just a text. Empty value coming from HTML form just went into NULL value in database, neat. Probably the change is good from language/theory perspective, I don't know, I'm a simple man. It was easier, now I need more code to type.

There was a discussion about changing this behavior for 6 last year: https://dev.lucee.org/t/different-cfqueryparam-behavior-between-acf-and-lucee/2836/14

oh well, missed it... in language purity vs. real world application I'd chose the latter. CFML always been language+framework for me, a framework for web development, and language that supports it. Going to 'another language with web development capabilities' makes no sense to me, there's better options already. If CFML will not be a handy tool for webdev (language+framework), it loses its appeal, and it's better for devs to go into python or else bigger language market

One of the biggest benefits of Lucee is that when your code works in Lucee, it works in AFC without issue. This is because Lucee doesn't have a bunch of cobbled-together code under the hood trying to adjust for every good and bad change. This allows it to run faster, leaner, and overall a cleaner solution.