[PR #21739] [CLOSED] fix: drop unique index on tag(id) to fix duplicate-key errors #49302

New Issue

GiteaMirror · 2026-04-30T01:36:47-05:00

GiteaMirror commented

2026-04-30 01:36:47 -05:00

📋 Pull Request Information

Original PR: https://github.com/open-webui/open-webui/pull/21739
Author: @martional
Created: 2/22/2026
Status: ❌ Closed

Base: dev ← Head: fix/drop-tag-id-unique-index

📝 Commits (1)

0e4622c fix: drop unique index on tag(id) to fix duplicate-key errors

📊 Changes

1 file changed (+53 additions, -0 deletions)

View changed files

➕ backend/open_webui/migrations/versions/c8d4e5f6a7b8_drop_tag_id_unique_index.py (+53 -0)

📄 Description

fix: drop unique index on tag(id) to fix duplicate-key errors

Fixes #21737

Pull Request Checklist

Target branch: Targets the dev branch
Description: See below
Changelog: Added at bottom
Documentation: N/A – migration only
Dependencies: None
Testing: Migration is idempotent; tested logic matches existing migration patterns
Agentic AI Code: Human-reviewed and manually verified
Code review: Self-reviewed against project migration style
Title Prefix: fix

Description

Drops any leftover unique index on tag.id alone that conflicts with the composite primary key (id, user_id). In some upgrade paths or database engines, a unique index on id alone can persist from the original schema and cause UNIQUE constraint failed: tag.id (SQLite) or equivalent errors when multiple users create tags with the same name.

Changes:

Add migration c8d4e5f6a7b8_drop_tag_id_unique_index.py that inspects the tag table and drops any unique index on id alone if it exists
Migration is idempotent and safe: only drops indexes that match the problematic pattern
No downgrade (intentional: we don't recreate the problematic index)

Changelog Entry

Description

Add migration to drop unique index on tag.id when it conflicts with composite PK (id, user_id), fixing duplicate-key errors when multiple users create tags with the same name.

Fixed

Tag duplicate-key errors: UNIQUE constraint failed: tag.id (SQLite) / duplicate key violation (PostgreSQL) when different users create tags with the same name

Additional Information

Related issue: [PR #5674] [MERGED] 0.3.28 (#21737)
Migration 3ab32c4b8f59_update_tags.py attempted to drop conflicting indexes, but in some upgrade paths a unique index on id alone can persist. This migration explicitly drops such indexes if they exist.

Contributor License Agreement

By submitting this pull request, I confirm that I have read and fully agree to the Contributor License Agreement (CLA), and I am providing my contributions under its terms.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/open-webui/open-webui/pull/21739 **Author:** [@martional](https://github.com/martional) **Created:** 2/22/2026 **Status:** ❌ Closed **Base:** `dev` ← **Head:** `fix/drop-tag-id-unique-index` --- ### 📝 Commits (1) - [`0e4622c`](https://github.com/open-webui/open-webui/commit/0e4622c3ac9003fab496563302c768f6d8d40a49) fix: drop unique index on tag(id) to fix duplicate-key errors ### 📊 Changes **1 file changed** (+53 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `backend/open_webui/migrations/versions/c8d4e5f6a7b8_drop_tag_id_unique_index.py` (+53 -0) </details> ### 📄 Description # fix: drop unique index on tag(id) to fix duplicate-key errors Fixes #21737 ## Pull Request Checklist - [x] **Target branch:** Targets the `dev` branch - [x] **Description:** See below - [x] **Changelog:** Added at bottom - [ ] **Documentation:** N/A – migration only - [ ] **Dependencies:** None - [x] **Testing:** Migration is idempotent; tested logic matches existing migration patterns - [x] **Agentic AI Code:** Human-reviewed and manually verified - [x] **Code review:** Self-reviewed against project migration style - [x] **Title Prefix:** fix ## Description Drops any leftover unique index on `tag.id` alone that conflicts with the composite primary key `(id, user_id)`. In some upgrade paths or database engines, a unique index on `id` alone can persist from the original schema and cause `UNIQUE constraint failed: tag.id` (SQLite) or equivalent errors when multiple users create tags with the same name. **Changes:** - Add migration `c8d4e5f6a7b8_drop_tag_id_unique_index.py` that inspects the tag table and drops any unique index on `id` alone if it exists - Migration is idempotent and safe: only drops indexes that match the problematic pattern - No downgrade (intentional: we don't recreate the problematic index) --- # Changelog Entry ### Description - Add migration to drop unique index on `tag.id` when it conflicts with composite PK `(id, user_id)`, fixing duplicate-key errors when multiple users create tags with the same name. ### Fixed - Tag duplicate-key errors: `UNIQUE constraint failed: tag.id` (SQLite) / duplicate key violation (PostgreSQL) when different users create tags with the same name ### Additional Information - Related issue: #21737 - Migration `3ab32c4b8f59_update_tags.py` attempted to drop conflicting indexes, but in some upgrade paths a unique index on `id` alone can persist. This migration explicitly drops such indexes if they exist. ### Contributor License Agreement By submitting this pull request, I confirm that I have read and fully agree to the [Contributor License Agreement (CLA)](https://github.com/open-webui/open-webui/blob/main/CONTRIBUTOR_LICENSE_AGREEMENT), and I am providing my contributions under its terms. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

GiteaMirror added the pull-request label 2026-04-30 01:36:47 -05:00

GiteaMirror closed this issue

2026-04-30 01:36:48 -05:00

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/open-webui#49302