I am wondering what the literal for a Null character (e.g. '\0') is in TSQL.
Note: not a NULL field value, but the null character (see link).
I have a column with a mix of typical and a null character. I'm trying to replace the null character with a different value. I would have thought that the following would work but it is unsuccessfull:
select REPLACE(field_with_nullchar, char(0), ',') from FOO where BAR = 20
In SQL, null or NULL is a special marker used to indicate that a data value does not exist in the database. Introduced by the creator of the relational database model, E. F.
A character literal is an individual character enclosed by single quotes (apostrophes). Character literals include all the printable characters in the PL/SQL character set: letters, numerals, spaces, and special symbols. PL/SQL is case sensitive within character literals.
A null character refers to any character that has a numeric value of zero. It is termed a null character as it doesn't carry a value and all its bit are set on 0. A null character is also known as a null terminator.
Literal SQL - SSIS. Literals are hard coded information that you must provide when building expressions. SSIS expressions have three types of literals: numeric, string, and Boolean. literal overflows the type.
There are two different behaviors in the Cade Roux's answer: replacement is successful (when SQL collation is used) and unsuccessful (Windows collation is used). The reason is in type of collation used.
This behaviour was submitted to Microsoft nearly 4 years ago:
Q: When trying a replace a NUL character with replace(), this works is the value has an SQL collation, but not a Windows collation.
A: This is due to the fact that 0x0000 is an undefined character in Windows collations. All undefined characters are ignored during comparison, sort, and pattern matching. So searing for 'a' + char(0) is really searching for ‘a’, and searching for char(0) is equivalent to empty string.
The way to handle undefined character is a bit confusing, but this is the way that Windows defined to sort them, and SQL Server conforms with the general Windows API.
In SQL collation, there is no notion of undefined character. Each code point is assigned a weight, that's why we don't see a problem there.
but unfortunately, it is still undocumented.
So, it seems the only one solution is to change collation to SQL collation (e.g. SQL_Latin1_General_CP1_CI_AS
may be used as well).
* I removed my previous answer as unnecessary
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With