Null, Empty Strings, And Efficiency

************* Edited by moderator Adec ***************


Inserted missing < code></ code> tags. Always include such


tags when including code in your postings. Don't force the


moderators to do this for you. Many readers disregard


postings without the code tags.


**************************************************





Well met,





Let's say I have a web form that allows users to insert and update records in a SQL database. Is it better to set empty web controls (textbox, etc.) to DBNull or let it go as an empty string into the database?





Example code:





if (tboxNAME.Text == "")


{


sqlCommand1.Parameters["@NAME"].Value = DBNull.Value;


}


else


{


sqlCommand1.Parameters["@NAME"].Value = tboxNAME.Text;


}





Is the above overkill? It seems like it would be a good idea to set fields which the user empties back to Null rather than an empty string.





Thanks,





-Tony