> For the complete documentation index, see [llms.txt](https://www.pranaypourkar.co.in/the-programmers-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.pranaypourkar.co.in/the-programmers-guide/database/sql-databases/sql-fundamentals/sql-data-types/character-types.md). # Character Types ## About **Character data types** are used to store **textual data**, such as names, addresses, and descriptions. SQL provides standard character types that most relational databases support, with slight variations. There are two main categories: 1. **Fixed-length** character types 2. **Variable-length** character types ## 1. **CHAR(n)** * Stores **fixed-length** character strings. * Always occupies `n` characters, **padding with spaces** if input is shorter. * Use when all values are known to have the same length (e.g., status codes, country codes). **Example:**\ `CHAR(5)` will store `'abc'` as `'abc '` (with two spaces). ## 2. **VARCHAR(n)** or **CHARACTER VARYING(n)** * Stores **variable-length** character strings. * Maximum length is `n`, but only uses as much space as needed. * More efficient for storing strings of varying length. **Example:**\ `VARCHAR(10)` can store `'abc'` using 3 characters instead of 10. ## 3. **TEXT** (non-standard, vendor-specific) * Stores large text data (longer than `VARCHAR(n)` limits). * Not part of standard SQL but supported by many databases. ## Vendor Support Overview
DatabaseCHARVARCHARTEXT SupportNotes
OracleYesYesNo TEXT; use CLOBOracle uses CLOB for large character data. VARCHAR2 is preferred.
MySQLYesYesYesSupports TINYTEXT, TEXT, MEDIUMTEXT, LONGTEXT.
PostgreSQLYesYesYesTEXT has no length limit and behaves like unlimited VARCHAR.
SQL ServerYesYesYes (TEXT deprecated)Use VARCHAR(MAX) instead of TEXT.
SQLiteYesYesYesVery flexible typing; TEXT used commonly.
--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://www.pranaypourkar.co.in/the-programmers-guide/database/sql-databases/sql-fundamentals/sql-data-types/character-types.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.