[PR #894] [MERGED] fix(sqlite): id column should be unique #849

New issue

Closed

opened 2026-02-25 23:35:40 +03:00 by kerem · 0 comments

kerem commented

2026-02-25 23:35:40 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/go-shiori/shiori/pull/894
Author: @Monirzadeh
Created: 4/27/2024
Status: ✅ Merged
Merged: 5/12/2024
Merged by: @fmartingr

Base: master ← Head: fix-sqlite-uniq-id

📝 Commits (3)

555cddb id now is uniq in sqlite too
ea648ad Merge branch 'master' into fix-sqlite-uniq-id
5fa2f1a Merge branch 'master' into fix-sqlite-uniq-id

📊 Changes

2 files changed (+23 additions, -0 deletions)

View changed files

➕ internal/database/migrations/sqlite/0003_uniq_id.up.sql (+22 -0)
📝 internal/database/sqlite.go (+1 -0)

📄 Description

This PR try to fix #892

_{🔄 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/go-shiori/shiori/pull/894 **Author:** [@Monirzadeh](https://github.com/Monirzadeh) **Created:** 4/27/2024 **Status:** ✅ Merged **Merged:** 5/12/2024 **Merged by:** [@fmartingr](https://github.com/fmartingr) **Base:** `master` ← **Head:** `fix-sqlite-uniq-id` --- ### 📝 Commits (3) - [`555cddb`](https://github.com/go-shiori/shiori/commit/555cddb8dd9c590136d59c7d89b94fb413daff7b) id now is uniq in sqlite too - [`ea648ad`](https://github.com/go-shiori/shiori/commit/ea648adb83e80359cef50750cc10820972151b2e) Merge branch 'master' into fix-sqlite-uniq-id - [`5fa2f1a`](https://github.com/go-shiori/shiori/commit/5fa2f1a190e19ec64b2be4ddb9f5a4e1fe4a38db) Merge branch 'master' into fix-sqlite-uniq-id ### 📊 Changes **2 files changed** (+23 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `internal/database/migrations/sqlite/0003_uniq_id.up.sql` (+22 -0) 📝 `internal/database/sqlite.go` (+1 -0) </details> ### 📄 Description This PR try to fix #892 --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>