Number of expected violations when using multiple conditions (both ANY and ALL)

[malice00]

I was thinking about a solution for #2146 and am unsure of how to continue, so I figured I'd start a discussion to see how others think about this.

Currently, if a policy with multiple conditions is defined (either ANY or ALL operator doesn't really matter), all conditions are validated and violations are created. I already created a PR to only save the violations for ALL operator if they indeed all fail -- it however still creates multiple violations: 1 for each condition.

#2146 mentions this for the ALL operator, however thinking about this (and then testing it) made me realize the ANY operator actually does this as well. Personally I was expecting either operators to only show a single violation, but since nobody has reported this issue for the ANY operator, I would like some input from the community.

So, is the current implementation OK for the ANY operator, or should both operators be changed to only show a single violation -- probably with information which condition(s) are responsible for this violation?

[malice00]

So, I've been working on this for a bit and I now have some more questions...

1. I've made some changes in the model, which are reflected in the database as well. In one of the tables, a column is no longer used --> seeing it is not automatically deleted, I was wondering if I can just delete it, or leave it and ignore it (after setting it to nullable)?
2. I need a new column in another table that should be non-nullable, but since there might already be data in it, this throws an exception when starting up DT --> is it OK to define the field (and therefor the column) as nullable? If so, can/should I manually set it to non-nullable after filling in the missing data?
3. What would be the correct way to get a value for the UUID-column in my new table?