I suggest you ...

set NullValue to "(Null)" instead of "throw exception" by default in dataset designer

In dataset designer, by default "NullValue" of DataColumns is "throw exception".
It's rather tricky to handle such exceptions.
I'm quite sure it makes more sense to return null directly (or at least return DBNUll) by default. This is because I do not want to an exception every time when DBNull is returned as null is valid in most cases. If it's not valid, I can still get NullReferenceException. Why should it throw one more exception?
If you do not agree with me, you may do an poll.
However, of course, you can leave "throw exception" as an option.

1 vote
Vote
Sign in
(thinking…)
Sign in with: facebook google
Signed in as (Sign out)
You have left! (?) (thinking…)
Leon Zeng shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

Thank you for your suggestion! While we aim to respond to every suggestion, we are closing older ones that don’t have enough votes so newer ones from you can move to the top. If this suggestion is still important to you, feel free to open it again.

1 comment

Sign in
(thinking…)
Sign in with: facebook google
Signed in as (Sign out)
Submitting...
  • Leon Zeng commented  ·   ·  Flag as inappropriate

    Per my understanding, null is not applicable for int/DateTime etc, but for string, byte[] etc it's fine.

Feedback and Knowledge Base