MySQL ERROR 1066 (42000): Not unique table/alias: 'x'
The same table or alias appears twice in a FROM/JOIN without distinct aliases.
Exact message you may see
Not unique table/alias
Seen on:
SQL
Meaning
Self-joins and repeated joins need different aliases. ORMs joining the same relation twice can produce this.
Common causes
- Self-join without aliases
- Joining the same table twice
- ORM eager loads duplicating joins
⚡ Quick fix
- Give each occurrence its own alias (u1, u2)
- Check ORM eager-loading config if the SQL is generated
Detailed fix by platform
SQL
SELECT e.name, m.name AS manager FROM employees e JOIN employees m ON m.id = e.manager_id;
How to diagnose
- Alias — Which name repeats?
- Recent change — Did it start after a deploy, upgrade, or configuration change? Compare with the last working version.
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
Most viewed in SQL
Other ways to find it
Where this error sits
Origin: Data. Errors that are often confused with or caused by this one (click to open):
🧠 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.
Did this fix work for you?
Report a correction or suggest an improvement
Last updated 13 Oct 2026