I’m getting this error when trying to update via ./launcher rebuild app ActiveRecord::RecordNotUnique: PG::UniqueViolation: ERROR: could not create unique index "index_discourse_solved_solved_topics_on_answer_post_id" (ActiveRecord::RecordNotUnique) DETAIL: Key (answer_post_id)=(201795) is dupli…

Seems to be fixed with this patch: FIX: Multiple topics may have the same post as its solution (#348) committed 02:21PM - 26 Mar 25 UTC (UTC) [Bild] nattsw …

Delete one of the SolvedTopic records via rails console: DiscourseSolved::SolvedTopic.where(answer_post_id:201795).last.destroy

Thank you. I’ve tried to access those, but I’m getting NameError: uninitialized constant SolvedTopic Any other ideas?

I’ve now connected to the database directly and deleted the record with the duplicate answer_post_id from discourse_solved_solved_topics. All good now. Thanks again for your quick reply!

Hm. discourse-solved was updated recently . There is a chance, that this error was thrown during database migration.

Yes, this happened during database migration.

Excellent! Thanks for the heads up — I’ve marked your post as solution.

FEHLER RecordNotUnique auf Index_discourse_solved_solved_topics_on_answer_post_id

Unterstützung

fhe (Florian) 26. März 2025 um 17:07 9

Ausgezeichnet! Danke für die Info — Ich habe Ihren Beitrag als Lösung markiert.

Thema		Antworten	Aufrufe
"discourse_solved_solved_topics" violates not-null constraint during rebuild Support solved	9	160	21. Dezember 2025
Cannot restore database: sql key is duplicated Self-hosting	2	579	30. August 2022
Restore fails - could not create unique index Self-hosting	22	3971	6. Juli 2020
Update failed - PG::UniqueViolation: ERROR Self-hosting	8	844	14. November 2021
Error restoring backup "key is duplicated" Self-hosting	8	1844	31. August 2017

FEHLER RecordNotUnique auf Index_discourse_solved_solved_topics_on_answer_post_id

Verwandte Themen