Details

    • Type: Explanation
    • Status: Obsolete
    • Affects Version/s: EXASolution 4.1.0, EXASolution 4.2.0, EXASolution 5.0, EXASOL 6.0.0, Exasol 6.1.0, Exasol 6.2.x
    • Fix Version/s: None
    • Component/s: EXASolution
    • Labels:
    • Explanation:
      Hide

      Note: This solution is no longer maintained. For the latest information, please visit our Knowledge Base:

      https://community.exasol.com/t5/database-features/unicode-support-in-exasol/ta-p/775

      ------------------------------------------------------------------------------------------------------------------------------------------------------------------

      Background

      Unicode is a computing industry standard (ISO 10646)allowing computers to consistently represent and manipulate text expressed in most of the world's writing systems. With text processing, Unicode takes the role of providing a unique code point — a number, not a glyph — for each character. In other words, Unicode represents a character in an abstract way and leaves the visual rendering (size, shape, font or style) to other software, such as a web browser or word processor.

      Explanation

      Unicode has the explicit aim of transcending the limitations of traditional character encodings, which find wide usage in various countries of the world but remain largely incompatible with each other.

      EXASolution fully supports Unicode and can, therefore, store all the common characters in der database. All identifiers such as schema, table or column names can contain Unicode-characters. You don't need any special settings at table creation (f.e. CREATE TABLE t (v VARCHAR(50)) either. Internally a well-established UTF-8 format will be used, which stores Unicode-characters as variable-length ones. The data type defines the number of symbols that can be stored, not the length in bytes.

      On the client-side, the corresponding database driver (f.e. JDBC, ODBC or Client SDK) converts data from local characters set to UTF-8 format and vice versa. Hense the database user can work with the same data by using different character sets without paying any attention to it.

      Show
      Note: This solution is no longer maintained. For the latest information, please visit our Knowledge Base: https://community.exasol.com/t5/database-features/unicode-support-in-exasol/ta-p/775 ------------------------------------------------------------------------------------------------------------------------------------------------------------------ Background Unicode is a computing industry standard (ISO 10646)allowing computers to consistently represent and manipulate text expressed in most of the world's writing systems. With text processing, Unicode takes the role of providing a unique code point — a number, not a glyph — for each character. In other words, Unicode represents a character in an abstract way and leaves the visual rendering (size, shape, font or style) to other software, such as a web browser or word processor. Explanation Unicode has the explicit aim of transcending the limitations of traditional character encodings, which find wide usage in various countries of the world but remain largely incompatible with each other. EXASolution fully supports Unicode and can, therefore, store all the common characters in der database. All identifiers such as schema, table or column names can contain Unicode-characters. You don't need any special settings at table creation (f.e. CREATE TABLE t (v VARCHAR(50)) either. Internally a well-established UTF-8 format will be used, which stores Unicode-characters as variable-length ones. The data type defines the number of symbols that can be stored, not the length in bytes. On the client-side, the corresponding database driver (f.e. JDBC, ODBC or Client SDK) converts data from local characters set to UTF-8 format and vice versa. Hense the database user can work with the same data by using different character sets without paying any attention to it.
    • Category 1:
      SQL - Data types

      Attachments

        Activity

          People

          • Assignee:
            CaptainEXA Captain EXASOL
            Reporter:
            CaptainEXA Captain EXASOL
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: