Skip to content

[newfeature]: alias + constraints #130

@leblancmeneses

Description

@leblancmeneses

Aliasing docs state "When evaluating constraints, only the first name counts."

I missed the statement above when working through this sample:

Quantity: 0, 2, 1|3|4|5
Quantity1: <Quantity>
Quantity2: <Quantity>


If [Quantity2] > [Quantity1]
  THEN [Quantity2] = [Quantity1];

results in 11 rows:

Quantity,Quantity1,Quantity2
2,2,1
2,0,0
0,2,0
2,2,2
1,0,0
0,0,0
0,1,3 -- unexpected; 0,1,1 or  0,1,0 would have worked.
2,3,0
3,2,2
4,4,4
0,2,2

The only way I know to fix this is to remove the alias: Quantity: 0, 2, 1,3,4,5
which explodes the results to 48 but my constraint is kept intact.

A warning that a constraint was ignored due to an alias rule would be a welcomed change.
However, given it is an alias why couldn't the row be mutated so that it met my constraint?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions