NULL value in @Message results in Error when inserting in Log4Net table


If you provide NULL in one of the following Log4Net logging table columns, Log4TSQL will throw an error in prc_RayLog when trying to insert a new row in the logging table:
The next release will be more fault tolerant - but only regarding a NULL value in @Message (for performance reasons) since you may concatenate a string with NULL - which results in NULL - and then pass it with the @LogMessage-parameter.
Closed Sep 14, 2009 at 8:58 PM by Audience
Fixed in Version 1.06