SQL Server

StringBuilder Encode Charset

Demonstrates the importance of the charset argument when encoding/decoding. SQL Server

-- Important: See this note about string length limitations for strings returned by sp_OAMethod calls.
--
CREATE PROCEDURE ChilkatSample
AS
BEGIN
    DECLARE @hr int
    -- Important: Do not use nvarchar(max).  See the warning about using nvarchar(max).
    DECLARE @sTmp0 nvarchar(4000)
    DECLARE @s nvarchar(4000)
    SELECT @s = 'é é é'

    DECLARE @sb int
    EXEC @hr = sp_OACreate 'Chilkat.StringBuilder', @sb OUT
    IF @hr <> 0
    BEGIN
        PRINT 'Failed to create ActiveX component'
        RETURN
    END

    DECLARE @success int
    EXEC sp_OAMethod @sb, 'Append', @success OUT, @s
    EXEC sp_OAMethod @sb, 'EntityDecode', @success OUT

    -- The string now contains: "é é é"
    EXEC sp_OAMethod @sb, 'GetAsString', @sTmp0 OUT
    PRINT @sTmp0

    -- If encoded to hex using the iso-8859-1 charset, 
    -- each é char is represented in 1 byte.
    -- Output: E920E920E9
    EXEC sp_OAMethod @sb, 'GetEncoded', @sTmp0 OUT, 'hex', 'iso-8859-1'
    PRINT @sTmp0

    -- If encoded to hex using the utf-8 charset, 
    -- each é char is represented in 2 bytes.
    -- Output: C3A920C3A920C3A9
    EXEC sp_OAMethod @sb, 'GetEncoded', @sTmp0 OUT, 'hex', 'utf-8'
    PRINT @sTmp0

    -- Here's utf-16
    -- Output: E9002000E9002000E900
    EXEC sp_OAMethod @sb, 'GetEncoded', @sTmp0 OUT, 'hex', 'utf-16'
    PRINT @sTmp0

    -- utf-32
    -- Output: E900000020000000E900000020000000E9000000
    EXEC sp_OAMethod @sb, 'GetEncoded', @sTmp0 OUT, 'hex', 'utf-32'
    PRINT @sTmp0

    EXEC @hr = sp_OADestroy @sb


END
GO