#3933 closed Bug (fixed)

Segmentation: NOT EQUAL != and DOES NOT CONTAIN !@ should also match the rows with NULL values

Reported by: matt Owned by: mattab
Priority: normal Milestone: 1.12 - The Great 1.x Backlog
Component: Core Keywords:
Cc: Sensitive: no

Description

Imagine the request:

  • Visitors where Custom variable 1 IS NOT "test".

I think this segmentation request should match and include in the dataset, the visitors that had a Custom var1 "hello" or "type" but also those that did NOT have a custom variable 1 set.

This ticket is about changing the API so that when EXCLUDING visitors, we dont exclude those for which the value was not set.

If you wish to also exclude the visitors for which the value was NOT set, then you can use the IS NULL match eg. referrerKeyword==;browserCode==ff will select all visitors that use Firefox and did NOT Have a keyword set. see #3932

Change History (1)

comment:1 Changed 11 months ago by matt (mattab)

  • Owner set to mattab
  • Resolution set to fixed
  • Status changed from new to closed

In d89a08b8b27ef9a7293e9f8cf351bedbd838e2cb:

Fixes #3932

  • you can now write browserCode==ff;referrerKeyword!= to select all visitors using firefox and that have a keyword set
  • or you can write referrerKeyword==;browserCode==ff to select all visitors using firefox and that did not have any keyword set

Also fixes #3933

Refs #2135

  • fixing last bugs with segment selector encoding (working on chrome + FF + opera) - I 'hope' it will work on iE...
Note: See TracTickets for help on using tickets.