varbinary handling different between LinqPad 8 and 9

I have a table with a row having various fields one of them is nullable varbinary. Using LinqPad 8 I can add a new row and the field defined as nullable varbinary stays null if not set.
Using LinqPad 9 the nullable binary is preset with 0x which is not desired. Can the default behaviour be configured or is this just a bug/feature?

Best Answer

Answers