String collation and sort order in PostgreSQL - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is collation in the context of databases?

Collation is a set of rules that determine how strings are compared and sorted in a database. It affects the order of letters, case sensitivity, and accents.

beginner

How does PostgreSQL use collation when sorting text data?

PostgreSQL uses the collation setting to decide how to order text data. It compares strings based on locale rules, which can affect case, accents, and character order.

intermediate

What happens if you do not specify a collation in a PostgreSQL query?

If no collation is specified, PostgreSQL uses the default collation of the database or the column, which is usually set when the database was created.

intermediate

How can you specify a collation for a column in PostgreSQL?

You can specify a collation for a column when creating or altering a table using the COLLATE keyword, for example: CREATE TABLE t (name TEXT COLLATE "en_US.UTF-8");

intermediate

Why might sorting results differ between two databases with the same data?

Sorting can differ because each database might use a different collation or locale setting, which changes how characters are compared and ordered.

What does collation affect in a database?

A How strings are compared and sorted

B The size of the database

C The speed of queries unrelated to text

D The number of tables

Collation controls how strings are compared and sorted, including case and accent sensitivity.

In PostgreSQL, what is the default collation used if none is specified?

A UTF-8 collation

B The collation of the operating system

C The database or column default collation

D No collation is used

PostgreSQL uses the database or column default collation if none is specified in the query.

How do you specify a collation for a column in PostgreSQL?

A Using the ORDER BY clause

B Using the CREATE INDEX command

C Using the SET command

D Using the COLLATE keyword

The COLLATE keyword is used to specify collation for columns or expressions.

Which of these can affect string sorting order?

A Table size

B Locale settings

C Number of rows

D Primary key type

Locale settings influence collation rules, which affect string sorting order.

If two databases have different collations, what might differ?

A The order of sorted text results

B The number of tables

C The data types supported

D The network speed

Different collations can cause text to be sorted in different orders.

Explain what collation is and why it matters when sorting text in a database.

Think about how letters and accents are ordered in different languages.

Describe how you can control string sorting order in PostgreSQL using collation.

Consider how you might want to sort names differently depending on language.

Practice

1. What does COLLATE do in a PostgreSQL query?

easy

A. It encrypts string data for security.

B. It controls how strings are sorted and compared based on language rules.

C. It changes the data type of a string column.

D. It creates an index on a string column.

Solution

1. Step 1: Understand COLLATE purpose

   COLLATE specifies the rules for sorting and comparing text, often based on language or locale.

2. Step 2: Differentiate from other functions

   COLLATE does not change data type, encrypt data, or create indexes; it only affects text ordering and comparison.

3. Final Answer:

   It controls how strings are sorted and compared based on language rules. -> Option B

4. Quick Check:

   COLLATE = sorting/comparison rules [OK]

Hint: COLLATE changes text sorting rules, not data type or encryption [OK]

Common Mistakes:

• Thinking COLLATE changes data type
• Confusing COLLATE with encryption
• Assuming COLLATE creates indexes

2. Which of the following is the correct syntax to sort a column name using the French collation in PostgreSQL?

easy

A. SELECT * FROM users ORDER BY COLLATE name 'fr_FR';

B. SELECT * FROM users ORDER BY name COLLATE fr_FR;

C. SELECT * FROM users ORDER BY name USING COLLATE 'fr_FR';

D. SELECT * FROM users ORDER BY name COLLATE 'fr_FR';

Solution

1. Step 1: Recall correct COLLATE syntax

   The correct syntax places COLLATE after the column name, followed by the collation name in single quotes.

2. Step 2: Check each option

   SELECT * FROM users ORDER BY name COLLATE 'fr_FR'; matches the correct syntax: ORDER BY name COLLATE 'fr_FR'. SELECT * FROM users ORDER BY COLLATE name 'fr_FR'; misplaces COLLATE. SELECT * FROM users ORDER BY name USING COLLATE 'fr_FR'; uses invalid keyword USING. SELECT * FROM users ORDER BY name COLLATE fr_FR; misses quotes around collation name.

3. Final Answer:

   SELECT * FROM users ORDER BY name COLLATE 'fr_FR'; -> Option D

4. Quick Check:

   ORDER BY column COLLATE 'locale' [OK]

Hint: Use ORDER BY column COLLATE 'locale' with quotes [OK]

Common Mistakes:

• Omitting quotes around collation name
• Placing COLLATE before column name
• Using USING keyword incorrectly

3. Given the table words with a column text containing values: 'apple', 'Äpple', 'banana', what is the result of this query?

SELECT text FROM words ORDER BY text COLLATE "C";

medium

A. ['Äpple', 'apple', 'banana']

B. ['apple', 'Äpple', 'banana']

C. ['apple', 'banana', 'Äpple']

D. ['banana', 'apple', 'Äpple']

Solution

1. Step 1: Understand COLLATE "C" behavior

   COLLATE "C" sorts based on byte values in UTF-8 encoding.

2. Step 2: Apply sorting to values

   Byte-wise: 'apple' starts with 0x61 ('a'), 'banana' with 0x62 ('b'), 'Äpple' with 0xC3 ('Ä'); 0x61 < 0x62 < 0xC3, so order is 'apple', 'banana', 'Äpple'.

3. Final Answer:

   ['apple', 'banana', 'Äpple'] -> Option C

4. Quick Check:

   COLLATE "C" sorts by byte order [OK]

Hint: COLLATE "C" sorts by byte values [OK]

Common Mistakes:

• Assuming locale-aware sorting with COLLATE "C"
• Thinking 'Äpple' comes before 'apple'
• Ignoring byte order sorting

4. You run this query but get an error:

SELECT * FROM products ORDER BY name COLLATE 'unknown_locale';

What is the likely cause?

medium

A. The collation 'unknown_locale' does not exist on the system.

B. The column name must be in double quotes.

C. COLLATE cannot be used in ORDER BY clause.

D. You must specify COLLATE before the column name.

Solution

1. Step 1: Identify error cause

   PostgreSQL throws an error if the specified collation name is not installed or recognized by the system.

2. Step 2: Check other options

   Column names do not require quotes unless case-sensitive; COLLATE is valid in ORDER BY; COLLATE must come after column name, which is correct here.

3. Final Answer:

   The collation 'unknown_locale' does not exist on the system. -> Option A

4. Quick Check:

   Invalid collation name causes error [OK]

Hint: Check collation name exists on system to avoid errors [OK]

Common Mistakes:

• Assuming COLLATE syntax is wrong
• Forgetting to install locale on OS
• Misplacing COLLATE keyword

5. You want to display a list of city names sorted according to German rules, but with case-insensitive sorting (e.g., 'Berlin' and 'berlin' treated the same). Which PostgreSQL approach is best?

hard

A. Use ORDER BY LOWER(city) COLLATE 'de_DE' ASC to sort case-insensitively with German collation.

B. Use ORDER BY city COLLATE 'de_DE' ASC and convert city to lowercase in SELECT.

C. Use ORDER BY city COLLATE 'C' ASC for fastest sorting.

D. Use ORDER BY city without COLLATE and rely on default sorting.

Solution

1. Step 1: Understand case-insensitive sorting need

   Sorting should ignore case but respect German language rules.

2. Step 2: Apply LOWER() with German collation

   Using LOWER(city) converts all to lowercase, then COLLATE 'de_DE' sorts according to German rules case-insensitively.

3. Step 3: Evaluate other options

   Use ORDER BY city COLLATE 'de_DE' ASC and convert city to lowercase in SELECT. sorts original case but does not affect sorting order; Use ORDER BY city COLLATE 'C' ASC for fastest sorting. uses byte sorting ignoring language rules; Use ORDER BY city without COLLATE and rely on default sorting. uses default locale which may not be German.

4. Final Answer:

   Use ORDER BY LOWER(city) COLLATE 'de_DE' ASC to sort case-insensitively with German collation. -> Option A

5. Quick Check:

   LOWER() + COLLATE for case-insensitive locale sort [OK]

Hint: Use LOWER() with COLLATE for case-insensitive locale sorting [OK]

Common Mistakes:

• Ignoring case by not using LOWER()
• Using COLLATE 'C' which ignores locale
• Relying on default locale for German sorting