Accept NULL value wherever a value is expected #72
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem raised on the ADQL validator project:
ivoa/lyonetia#16 (comment)
NULL is not allowed anywhere else than in
IS [NOT] NULL
andCAST(...)
. In all DBMS, NULL is valid value in almost all places where a value is expected. This is actually a miss in ADQL-2.0. This Pull-Request aims to fix this issue. An Erratum will be added to ADQL-2.0 document.