MOTOSHARE 🚗🏍️
Turning Idle Vehicles into Shared Rides & Earnings

From Idle to Income. From Parked to Purpose.
Earn by Sharing, Ride by Renting.
Where Owners Earn, Riders Move.
Owners Earn. Riders Move. Motoshare Connects.

With Motoshare, every parked vehicle finds a purpose. Owners earn. Renters ride.
🚀 Everyone wins.

Start Your Journey with Motoshare

Fixing Laravel Migration Error: “Unknown Collation: utf8mb4_0900_ai_ci”

While working with Laravel and MySQL, you might run into an error during migrations like this one:

Illuminate\Database\QueryException
SQLSTATE[HY000]: General error: 1273 Unknown collation: 'utf8mb4_0900_ai_ci'

Why This Happens

The collation utf8mb4_0900_ai_ci is introduced in MySQL 8.0. If you’re using an older version of MySQL (like 5.7 or earlier), it doesn’t recognize this collation, and Laravel throws this error during migrations or queries.

Laravel 10+ and Laravel 11 use this collation by default in their database config, assuming the database supports it.


How to Fix It

There are two common ways to fix this issue:

🛠 Option 1: Downgrade the Collation in config/database.php

Open the config/database.php file in your Laravel project.

Locate the mysql connection settings and change the collation and charset like this:

'mysql' => [
    'driver' => 'mysql',
    'host' => env('DB_HOST', '127.0.0.1'),
    'port' => env('DB_PORT', '3306'),
    'database' => env('DB_DATABASE', 'your_db_name'),
    'username' => env('DB_USERNAME', 'root'),
    'password' => env('DB_PASSWORD', ''),
    'charset' => 'utf8mb4',
    'collation' => 'utf8mb4_unicode_ci', // Change this line
    ...
],

Then, clear the config cache:

php artisan config:clear

Now try running the migration again:

php artisan migrate

Option 2: Upgrade Your MySQL Server

If possible, upgrade your MySQL server to version 8.0 or higher, which fully supports utf8mb4_0900_ai_ci.

This is ideal for production servers or when you need access to newer MySQL features.

This is a common issue when developing Laravel apps locally on XAMPP, WAMP, or older MySQL versions. Fortunately, a simple config change is usually all you need to get back on track.

Pro Tip: Always make sure your development and production environments use compatible database versions and configurations to avoid such surprises.

Related Posts

Secure by Design: The DevSecOps Transformation

In an era where cyber threats evolve daily, security can no longer be an afterthought in software development. The DevSecOps Training methodology represents a fundamental shift, integrating…

Building Unbreakable Systems: America’s Journey to Security-First Digital Excellence

Across the United States, from Silicon Valley’s innovation hubs to New York’s financial centers and emerging tech scenes nationwide, a quiet revolution is transforming how organizations approach…

Building Cyber-Resilient Futures: The UK’s Path to Security-First Digital Excellence

In the dynamic heart of the United Kingdom’s technology sector, a profound transformation is reshaping how organizations approach digital innovation. From the global financial centers of London…

Secure by Design: The Netherlands’ Blueprint for Digital Resilience

In the heart of Europe’s digital landscape, the Netherlands is pioneering a revolutionary approach to technology that places security at the core of innovation. From the historic…

Secure by Design: The New Paradigm Shaping India’s Tech Future

In the bustling tech corridors of Bangalore, the emerging innovation hubs of Hyderabad, and the established engineering centers of Chennai, a fundamental transformation is reshaping how software…

Mastering Security in the Canadian Tech Landscape: A Guide to Modern Practices

In the heart of Canada’s booming tech ecosystem—from the financial hubs of Toronto to the AI innovation centers of Montreal—a silent revolution is reshaping how software is…

0 0 votes
Article Rating
Subscribe
Notify of
guest
0 Comments
Oldest
Newest Most Voted
Inline Feedbacks
View all comments
0
Would love your thoughts, please comment.x
()
x