stackoverflow June 19, 2026 product Rep: 187

Why does a GridDB TQL predicate containing NULL-valued columns return different results than equivalent client-side filtering?

Score

Answers

Views

18.5

Trend Score

Question Details

No question body available.

Answers (1)

June 19, 2026 Score: 2 Rep: 790,930 Quality: Low Completeness: 40%

Some SQL dialects have as the null-safe equality operator. But as far as I can tell, TQL doesn't have this. It also doesn't have COALESCE() (if it did you could use COALESCE(region, '') != 'US').

So you'll have to check for it explicitly.


SELECT * WHERE region IS NULL OR region != 'US'

Export Question Data

Export this question and its answers for further analysis or reporting.

Back to Questions

Why does a GridDB TQL predicate containing NULL-valued columns return different results than equivalent client-side filtering?

Question Details

Tags

Answers (1)

Analysis Metrics

Question Information

Actions

Related Questions

Export Question Data