►Your Take◄ Evaluating a "Number" against Null Value

BenHayat

In C#, if I compare NumberA>Number B and if NumbeA was 1 NumberB was null which means had no value, the evaluation returns "true".

Tonight, I tested that in Aware and returned "false". But I went and put a value of "0" in NumberB, then the evaluation would return "true".

Don't you think Aware should have returned "true" in the first place? Meaning 1 is greater than null?
I like to get your opinion and also if you had run into this case?

Thanks!

hpl123

Haven´t had problems with how it works and my first thought was that DEFINED isn´t the same "type" as UNDEFINED so the Aware IM rule is executed correctly.

BenHayat

hpl123 wrote
Haven´t had problems with how it works and my first thought was that DEFINED isn´t the same "type" as UNDEFINED so the Aware IM rule is executed correctly.

My point wasn't whether DEFINED is the same as UNDEFINED. I was saying 1 id greater than UNDEFINED.
In this case Aware should have returned true, because the value of 1 is always greater than UNDEFINED/null value. But it returns false.

tford

I agree with you Ben.

BenHayat

tford wrote
I agree with you Ben.

I brought this point up, because if you do any evaluation between number attribute and another number attribute that it's value is UNDEFINED/null (not zero), your filtering condition will break with wrong result.
Which means, when you define a Number Attribute, you must consciously set it's initial value to Zero, otherwise you will have problems.

crisg0112

BenHayat wrote
tford wrote
I agree with you Ben.

I brought this point up, because if you do any evaluation between number attribute and another number attribute that it's value is UNDEFINED/null (not zero), your filtering condition will break with wrong result.
Which means, when you define a Number Attribute, you must consciously set it's initial value to Zero, otherwise you will have problems.

From what I can see on SQL, UNDEFINED is just that ... it's NOT ZERO and NOT NULL.

I had an issue before where I need to pass 4 parameters into a stored procedure but the 4 fields are non mandatory. Aware just throws up all sorts of errors.

I ended up having to initialise the 4 parameters by checking if it is DEFINED. And then update it with NULL. That did the trick.

I think support should set UNDEFINED = NULL or explain what exactly is UNDEFINED 🙂

hpl123

Ben,
Your thoughts makes sense and I don´t know if the UNDEFINED value has a specific function or why it works as it does.

Support,
I would also like to know more about UNDEFINED, NULL etc..
Thanks

crisg0112

Could this be it?

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/undefined