In create_insert_statement(), we have the following logic:
The first problem is that we're inserting empty binaries when the type should not have empty binaries.
However, it could also be considered incorrect that we insert empty binaries for clustering columns when we have something that matches the "null value". This is to avoid inserting nulls for clustering columns. Of course, users may actually want to insert empty strings for columns, but I think that if they want that behavior, changing the null value is the correct way to do that.
I propose changing the "elif" statement to something like:
I set the fix version for this to 2.1.0. If we're not comfortable making this entire change in 2.1.0, we should at least remove the "not" in the elif and make the other changes for 2.1.1