Add support for database condition operator "NOT BETWEEN"

While looking at the patch I'm wondering whether there is any place where the available operators are documented.
This fix here could also simplify \Drupal\views\Plugin\views\filter\NumericFilter::opBetween a bit.

@stBorchert
Well this code:

    else {
      $this->query->addWhere($this->options['group'], db_or()->condition($field, $this->value['min'], '<=')->condition($field, $this->value['max'], '>='));
    }

could leverage this new operator.

Tests are needed to make sure that the operator works for all supported databases.

I think you are right stBorchert, the implementation of "NOT BETWEEN" is correct. The borders are not part of the "NOT BETWEEN" operator. I have checked all three supported databases and all three implement "NOT BETWEEN" without the borders. For me this is a bug and should be corrected. The problem is that you can also look at it with the view that this is a API change and that is not allowed. I have added the issue tag "Needs subsystem maintainers review". It would be nice if both subsystem maintainers from the database and views have a look at this.
If we are going to fix this then we should also fix the views part. The "NOT BETWEEN" operator works for numbers, strings and dates. We must be sure that for all three there is enough testing. Especially for the border stuff.

Changing the category to bug. See previous comment #10.

For me this is a bug and should be corrected. The problem is that you can also look at it with the view that this is a API change and that is not allowed. I have added the issue tag "Needs subsystem maintainers review".

I talked with @stborchert before about that, and given that the database API is working different, is a clear sign that this is a bug of views IMHO.

@stBorchert: According to the database documentation you can use "NOT BETWEEN" with numbers, dates and strings. I did not know that drupal did not use it with strings.

@dawehner: Thank you for your input.

The patch looks good to me.
All the changes for the database drivers are there.
All the changes for views are also there.
Changed so test for border cases. Views had a bug where borders where included in the result for "NOT BETWEEN" selections.
For me it is RTBC.

Good work stBorchert.

Revering before someone takes insult of me linking to the SQL standard.

Back to RTBC.

Committed and pushed f1d5d6595154453cebadfc39e7988499fb71a121 to 8.2.x and 8219239 to 8.1.x. Thanks!

One potential problem is that apparently not all databases do BETWEEN and NOT BETWEEN the same way - vis a vis - how the borders are included or not. But, as @chx added and then removed from the IS the ANSI standard SQL-92 is quite clear...

5) "X NOT BETWEEN Y AND Z" is equivalent to "NOT ( X BETWEEN Y AND
Z )".

6) "X BETWEEN Y AND Z" is equivalent to "X>=Y AND X<=Z".

So we cna't be responsible for other DBs bugs.

I thought about only committing this to 8.2.x because of the slight change in behaviour to views but I think this is a bug and ti does not matter when it is fixed.

I decided not to push because I realised that adding "not between" is a feature addition and therefore not eligible for 8.1.x and additionally as a feature addition should have a CR to tell people about it.

Added a change record.

Committed 5601e98 and pushed to 8.2.x. Thanks!

Back to fixed.

Typo in the change record:

"X NOT BETWEEN Y AND Z" is equivalent to "XZ"

Pretty sure it should be "XOR X>Z".

Type fixed.

Thanks drunken monkey!