Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

queryParam null=true doesn't work for QueryExecute

Description

Assuming we have a table like this:

Run the following code:

The first row with QueryExecute is inserted as an empty string(wrong), while the second with Query object is inserted as null(correct).

Environment

None

Attachments

4

Activity

Show:

Igal Sapir 25 August 2017 at 19:52

FYI: This is now resolved and deployed. I also tested for regressions and everything seems fine.

Igal Sapir 23 June 2017 at 20:51

I'll fix it soon. We just need to ensure that the fix doesn't introduce any new issues, or reintroduces old ones.

Nando 23 June 2017 at 20:49

I can't vote for this because it is marked as deployed, but this should be fixed.

Igal Sapir 14 June 2017 at 17:24

Micha has reverted this commit for now. the commented line was commented out when he fixed and we do not know ATM what implications uncommenting it might have. we need to check both this and 224 at the same time to ensure that the new fix doesn't break the old fix.

Former user 14 June 2017 at 07:44

thanks for that - regarding removing "nulls", I agree in principle, but in practise that would be a breaking change that breaks every instance where I've had to use "nulls" over the last many months waiting for the PR to be pulled in

Fixed

Details

Assignee

Reporter

Priority

Labels

Fix versions

New Issue warning screen

Before you create a new Issue, please post to the mailing list first https://dev.lucee.org

Once the issue has been verified, one of the Lucee team will ask you to file an issue

Sprint

Affects versions

Created 23 May 2015 at 08:01
Updated 8 September 2017 at 14:46
Resolved 13 August 2015 at 13:03