queryExecute() with list params doesn't seem to work right

In a CFC I have code that under ACF works as expected:

local.q= QueryExecute("
select …
from …
where
ee_groups.name in (:possGrps) and
ee_users.active=1
“,
{
email=arguments.email,
possGrps={value:valueList( local.all.name ),list:true}
},
{datasource=”#variables.dsn#"}
);

under Lucee 4.5.1 this results in SQL that contains

ee_groups.name in (‘column one value one, column one value two’)

rather than

ee_groups.name in (‘column one value one’, ‘column one value two’)

This is exactly like Lucee doesn’t see the “list” parameter to the
cfqueryparam. Using “Yes” instead of true is no help.

Can anyone confirm it before I raise a bug and then get told it’s my own
fault ?

Tom

And rewriting as

local.personQ=new Query(datasource=variables.dsn);


local.personQ.addParam(name=‘possGrps’,value=valueList( local.all.name
),list=true);
local.q=local.personQ.execute().getResult();

also fixes it.

Bug ?On 21 May 2015 at 11:33, Tom Chiverton <@Tom_Chiverton> wrote:

In a CFC I have code that under ACF works as expected:

local.q= QueryExecute("
select …
from …
where
ee_groups.name in (:possGrps) and
ee_users.active=1
“,
{
email=arguments.email,
possGrps={value:valueList( local.all.name ),list:true}
},
{datasource=”#variables.dsn#"}
);

under Lucee 4.5.1 this results in SQL that contains

ee_groups.name in (‘column one value one, column one value two’)

rather than

ee_groups.name in (‘column one value one’, ‘column one value two’)

This is exactly like Lucee doesn’t see the “list” parameter to the
cfqueryparam. Using “Yes” instead of true is no help.

Can anyone confirm it before I raise a bug and then get told it’s my own
fault ?

Tom


You received this message because you are subscribed to a topic in the
Google Groups “Lucee” group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/lucee/dNxSYln18-Q/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
lucee+unsubscribe@googlegroups.com.
To post to this group, send email to lucee@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/lucee/cf9c6617-8dc8-435a-87ce-555a613fe4e3%40googlegroups.com
https://groups.google.com/d/msgid/lucee/cf9c6617-8dc8-435a-87ce-555a613fe4e3%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.


Tom

You got me wrong.

I don’t receive any notifications regarding this issue updates, althought I
am “watching it”. I suppose it’s because of the migration from Bitbucket.

And the comments flow isn’t very helpful either to understand that this
issue had been acknowledged as a bug by the devs, an it will be fixed.On Friday, 22 May 2015 13:10:53 UTC+3, Adam Cameron wrote:

Well that’s not true is it? It’s been fixed and it’s currently in QA
(according to the ticket).

Are you annoyed that everyone didn’t drop everything and sort it out the
very moment you raised it? If it was that important to you, you could
have fixed it and submitted a pull req, right?


Adam

I mention this issue
here https://luceeserver.atlassian.net/browse/LDEV-224, but nobody seems to
care anyway.

Open a new issue to get some attention.On Friday, 22 May 2015 10:56:14 UTC+3, Tom Chiverton wrote:

As in a known one ? I couldn’t locate it in the issue tracker ?

Tom

On Thursday, May 21, 2015 at 10:34:07 PM UTC+1, Konstantinos Liakos wrote:

List=true dosn’t work for queryexecute params. It is a bug.

As in a known one ? I couldn’t locate it in the issue tracker ?

TomOn Thursday, May 21, 2015 at 10:34:07 PM UTC+1, Konstantinos Liakos wrote:

List=true dosn’t work for queryexecute params. It is a bug.

I mention this issue here
https://luceeserver.atlassian.net/browse/LDEV-224, but nobody seems to
care anyway
.

Well that’s not true is it? It’s been fixed and it’s currently in QA
(according to the ticket).

Are you annoyed that everyone didn’t drop everything and sort it out the
very moment you raised it? If it was that important to you, you could
have fixed it and submitted a pull req, right?On Friday, 22 May 2015 10:51:50 UTC+1, Konstantinos Liakos wrote:


Adam