Character types (char, varchar, text) in PostgreSQL - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the difference between char(n) and varchar(n) in PostgreSQL?

char(n) stores fixed-length strings and pads with spaces if shorter than n. varchar(n) stores variable-length strings up to n characters without padding.

beginner

What happens if you insert a string longer than the declared length into a varchar(n) column?

PostgreSQL will reject the insert and return an error because the string exceeds the maximum allowed length n.

beginner

How does the text type differ from varchar and char?

text stores strings of any length without a set limit. It is similar to varchar without a length limit and does not pad spaces like char.

intermediate

Why might you choose varchar(n) over text?

Using varchar(n) enforces a maximum length, which helps keep data consistent and can prevent accidental long inputs.

intermediate

Does char(n) always use more storage than varchar(n) for shorter strings?

Yes, because char(n) pads strings with spaces to the fixed length n, it can use more storage if the string is shorter than n.

Which PostgreSQL type stores strings with a fixed length and pads shorter strings with spaces?

A int

B varchar(n)

C text

D char(n)

char(n) stores fixed-length strings and pads with spaces if needed.

What happens if you insert a string longer than the limit into a varchar(n) column?

A It stores the full string ignoring the limit

B It throws an error and rejects the insert

C It truncates the string automatically

D It converts the string to <code>text</code> type

PostgreSQL rejects the insert with an error if the string exceeds the declared length.

Which type allows storing strings of any length without a set limit?

A text

B char(n)

C varchar(n)

D boolean

text can store strings of any length without a maximum limit.

Why might you use varchar(n) instead of text?

A To enforce a maximum string length

B Because <code>varchar</code> is faster for all queries

C Because <code>text</code> is deprecated

D To save storage space always

varchar(n) enforces a maximum length, helping keep data consistent.

Which type can use more storage for short strings due to padding?

A varchar(n)

B text

C char(n)

D integer

char(n) pads shorter strings with spaces, potentially using more storage.

Explain the differences between char(n), varchar(n), and text types in PostgreSQL.

Think about length limits and how strings are stored.

When would you choose varchar(n) over text for a column?

Consider data validation and input control.

Practice

1. Which PostgreSQL character type stores text with a fixed length, padding with spaces if the input is shorter?

easy

A. CHAR(n)

B. VARCHAR(n)

C. TEXT

D. INT

Solution

1. Step 1: Understand fixed-length storage

   CHAR(n) stores exactly n characters, padding with spaces if input is shorter.

2. Step 2: Compare with other types

   VARCHAR(n) stores variable length up to n, TEXT has no limit, INT is numeric.

3. Final Answer:

   CHAR(n) -> Option A

4. Quick Check:

   Fixed length with padding = CHAR(n) [OK]

Hint: Fixed length with padding means CHAR(n) [OK]

Common Mistakes:

• Confusing VARCHAR(n) as fixed length
• Thinking TEXT has length limit
• Choosing numeric types by mistake

2. Which of the following is the correct syntax to declare a variable-length character column with a maximum of 50 characters in PostgreSQL?

easy

A. CHAR(50)

B. VARCHAR(50)

C. TEXT(50)

D. STRING(50)

Solution

1. Step 1: Identify variable-length syntax

   VARCHAR(n) declares variable-length text with max n characters.

2. Step 2: Check other options

   CHAR(50) is fixed length, TEXT has no length limit, STRING is invalid in PostgreSQL.

3. Final Answer:

   VARCHAR(50) -> Option B

4. Quick Check:

   Variable length with max limit = VARCHAR(n) [OK]

Hint: Use VARCHAR(n) for variable length with max size [OK]

Common Mistakes:

• Using TEXT with length limit (invalid)
• Confusing CHAR as variable length
• Using non-existent STRING type

3. Consider the following table and insert statements:

CREATE TABLE users (name CHAR(5));
INSERT INTO users VALUES ('Tom');
SELECT name, LENGTH(name) FROM users;

What will be the output of the SELECT query?

medium

A. name = 'Tom ', length = 5

B. name = 'Tom', length = 3

C. name = 'Tom', length = 5

D. name = 'Tom ', length = 3

Solution

1. Step 1: Understand CHAR(5) behavior on insert

   CHAR(5) pads 'Tom' with 2 spaces to make length 5.

2. Step 2: LENGTH function counts all characters including spaces

   LENGTH('Tom ') returns 5 because spaces count.

3. Final Answer:

   name = 'Tom ', length = 5 -> Option A

4. Quick Check:

   CHAR pads spaces, LENGTH counts them [OK]

Hint: CHAR pads spaces; LENGTH counts all characters [OK]

Common Mistakes:

• Assuming LENGTH ignores trailing spaces
• Thinking CHAR stores variable length
• Confusing CHAR with VARCHAR behavior

4. You have a table with a column defined as VARCHAR(10). You try to insert a string of 15 characters. What will happen?

medium

A. The string is truncated to 10 characters and inserted

B. The string is padded with spaces to 15 characters

C. An error is raised and insertion fails

D. The string is inserted fully ignoring the limit

Solution

1. Step 1: Understand VARCHAR(n) length limit enforcement

   VARCHAR(10) limits input to 10 characters strictly.

2. Step 2: Behavior on exceeding length

   PostgreSQL raises an error if input exceeds declared length.

3. Final Answer:

   An error is raised and insertion fails -> Option C

4. Quick Check:

   Exceeding VARCHAR limit causes error [OK]

Hint: Exceeding VARCHAR(n) length causes error, no truncation [OK]

Common Mistakes:

• Assuming automatic truncation happens
• Thinking VARCHAR pads with spaces
• Believing PostgreSQL ignores length limits

5. You want to store user comments of any length without worrying about size limits. Which PostgreSQL data type should you choose and why?

hard

A. INT, because it stores numeric values efficiently

B. CHAR(255), because it fixes length and saves space

C. VARCHAR(255), because it limits length to 255 characters

D. TEXT, because it stores variable-length text with no size limit

Solution

1. Step 1: Identify requirement for unlimited length

   User comments can be very long, so no fixed or limited length is suitable.

2. Step 2: Compare data types for length limits

   TEXT stores variable-length text with no size limit, unlike CHAR or VARCHAR.

3. Step 3: Exclude irrelevant types

   INT is numeric and unsuitable for text storage.

4. Final Answer:

   TEXT, because it stores variable-length text with no size limit -> Option D

5. Quick Check:

   No size limit needed = TEXT [OK]

Hint: Use TEXT for unlimited length text storage [OK]

Common Mistakes:

• Choosing CHAR or VARCHAR with fixed limits
• Confusing numeric types with text
• Assuming VARCHAR can store unlimited text