collation SQL Origin: Data OSI layer 6 · Presentation Last updated 18 Nov 2026

SQLite: no such collation sequence: X

A column or query uses a collation SQLite doesn't know (such as utf8mb4_unicode_ci, or a custom one not registered).

Exact message you may see no such collation sequencesqlite3.OperationalError: no such collation sequence: utf8mb4_unicode_ciSQLITE_ERROR: no such collation sequenceno such collation sequence: unicode
Seen on: SQLite Python

Meaning

SQLite only has BINARY, NOCASE and RTRIM built in. Remove MySQL-style collations from the schema/queries, use COLLATE NOCASE, or register the collation in your driver (create_collation) before opening the database. A schema created by an app with a custom collation fails in the sqlite CLI.

Common causes

  • MySQL collation in SQL/DDL
  • Custom collation not registered on this connection
  • Opening an app's database in another tool
  • ORM migration generated the wrong collation
  • ICU collation not compiled in

⚡ Quick fix

  1. Use COLLATE NOCASE or BINARY
  2. Register the collation on every connection
  3. Drop/recreate indexes using the unknown collation

Detailed fix by platform

SQL

  1. CREATE TABLE users (email TEXT COLLATE NOCASE UNIQUE);

How to diagnose

  1. Collation — Built in?
  2. Registered — On connection?
  3. Schema — Uses a custom one?

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: Data. Errors that are often confused with or caused by this one (click to open):

1005 — MySQL ERROR 1005 (HY000): Can't create table (errno: 150 "Foreign key constraint is incorrectly formed") (MySQL)10051007 — MySQL ERROR 1007 (HY000): Can't create database 'x'; database exists (MySQL)10071008 — MySQL ERROR 1008 (HY000): Can't drop database 'x'; database doesn't exist (MySQL)10081051 — MySQL ERROR 1051 (42S02): Unknown table 'x' (MySQL)10511054 — MySQL ERROR 1054 (42S22): Unknown column in 'field list' (MySQL)10541060 — MySQL ERROR 1060 (42S21): Duplicate column name 'x' (MySQL)10601067 — MySQL ERROR 1067 (42000): Invalid default value for 'created_at' (MySQL)10671075 — MySQL ERROR 1075 (42000): Incorrect table definition; there can be only one auto column and it must be defined as a key (MySQL)1075collation

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.