if it is in string format then i would have just use this
setString("");//i think by placing empty quotes it works fine
One thing I am curious on is why would you want to store null for a salary???
It is always best to choose a value like -0.0001 for example for the suspended guy and 0 for the guy in progress
I am curious why would you not know the salary??
And how much would .001 change an average on numerical values
I forgot to mention what the point of not having null was : and it is namely the fact that someone will ask: why the heck is this strange number there
Can you make joins on nulls???
aren't they bad when you are analysing data?
Nulls may not make business sense in some scenarios, but I would use it before I'd use some arbitrary nonsense value.
Average these numbers: 10,000 15,000 and 20,000 (answer: 15,000)
Now do it again except include 0.01 (answer: 11250.0025)
Nonsense values could skew the results of some queries. (That's the point I was trying to make anyway.)
No, NULL does not equal NULL.