QueryExecute throws error when specifying list of numerics

Description

There is a deviation between how QueryExecute and new Query() behave in that QueryExecute does not seem to handle lists of integers in the same way as Query.

The following code will error indicating that the supplied string cannot be cast to a number value

However the following example will operate as intended and use the list of numerics as a list of numerics

Environment

None

Activity

Show:
tom chiverton
September 25, 2015, 11:22 AM

Can we get this into the 4.x release soon ?

I'm a little tired of months later still having to rewrite queryExecute() to new Query() just because we want to change the SQL from '=' to 'in'.

Former user
September 25, 2015, 11:26 AM

will chase up once he's back from holiday - whilst some of these I would be happy enough to merge, this one was a bit of a pig to fix so it really needs his approval before it's merged in unfortunately. I share your frustration on having to fall back to new Query().

Michael Offner
December 7, 2015, 12:53 PM
Igal Sapir
June 14, 2017, 5:21 PM
Edited

please add a testcase for this. we need to make sure that we don't break anything here when we work on - thanks!

Pothys - MitrahSoft
June 16, 2017, 5:42 AM

I've added a testcase for this ticket, It's working fine on latest version (5.2.2.48).

Pull Request: https://github.com/lucee/Lucee/pull/249

Assignee

Michael Offner

Reporter

Former user

Priority

Major

Labels

None

Fix versions

Affects versions

Configure