Good overview. Thanks. I'd like to add one thing to keep in mind. It seems easy to consider this and use is null instead. However the pitfall is, when you compare against a column value (e.g. in a join), where null values exist. Or when you use optional user inputs and try something like this: tbl.col = NVL({input}, tbl.col) When this columns contains nulls then this becomes tbl.col = null what fails. (Here the solution could be tbl.col = {input} or {input} is null) The danger is, when you get a good looking resultset and don't recognize, that you compare against null!
It's very clear and I love SQL series for beginners! Thanks a lot!
Concise and too easy to understand. Thanks, Adrian
Good overview. Thanks.
I'd like to add one thing to keep in mind.
It seems easy to consider this and use is null instead.
However the pitfall is, when you compare against a column value (e.g. in a join), where null values exist.
Or when you use optional user inputs and try something like this:
tbl.col = NVL({input}, tbl.col)
When this columns contains nulls then this becomes tbl.col = null what fails.
(Here the solution could be tbl.col = {input} or {input} is null)
The danger is, when you get a good looking resultset and don't recognize, that you compare against null!
Nice explanation 😊
Really clear videos, great stuff
You're explanations are crystal 👍
Good and well prepared. Thank you!
A cool tutorial! Thank you a lot!