# Rake posts:reorder\_posts dà errore \`UniqueViolation\` **URL:** \ **Category:** Bug\ **Tags:** fixed\ **Created:** [5 Febbraio 2023, 10:59am UTC](https://meta.discourse.org/t/rake-posts-reorder-posts-gives-uniqueviolation-error/254098 "2023-02-05T10:59:35Z")\ **Posts on this page:** 1\ **Showing post:** 1
**Author:** ![Julien\_Palard](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/julien_palard/32/198784_2.png) [@Julien\_Palard](https://meta.discourse.org/u/Julien_Palard)\ **Post date:** [5 Febbraio 2023, 10:59am UTC](https://meta.discourse.org/t/rake-posts-reorder-posts-gives-uniqueviolation-error/254098/1 "2023-02-05T10:59:35Z")
Contesto: Sto cercando di dividere un post. Per farlo, penso di dover: - Creare un nuovo post nell’argomento. - Modificare il contenuto di entrambi i post come desidero. - Cambiare il proprietario del post che ho creato per farlo corrispondere all’originale. - Cambiare il timestamp del post che ho creato per farlo corrispondere all’originale (magari aggiungendo qualche secondo). - Eseguire `posts:reorder_posts[topic_id]` per spostare la mia risposta nella posizione corretta nell’argomento. La prima cosa che ho provato è stata l’invocazione di `posts:reorder_post`, “solo per vedere”, ma è fallita: ```plaintext root@discourse1-app:/var/www/discourse# rake "posts:reorder_posts[879]" rake aborted! PG::UniqueViolation: ERROR: duplicate key value violates unique constraint "post_timings_unique" DETAIL: Key (topic_id, post_number, user_id)=(879, 93, 1) already exists. /var/www/discourse/vendor/bundle/ruby/3.1.0/gems/rack-mini-profiler-3.0.0/lib/patches/db/pg.rb:110:in `exec' /var/www/discourse/vendor/bundle/ruby/3.1.0/gems/rack-mini-profiler-3.0.0/lib/patches/db/pg.rb:110:in `async_exec' /var/www/discourse/vendor/bundle/ruby/3.1.0/gems/mini_sql-1.4.0/lib/mini_sql/postgres/connection.rb:209:in `run' /var/www/discourse/vendor/bundle/ruby/3.1.0/gems/mini_sql-1.4.0/lib/mini_sql/active_record_postgres/connection.rb:38:in `block in run' /var/www/discourse/vendor/bundle/ruby/3.1.0/gems/mini_sql-1.4.0/lib/mini_sql/active_record_postgres/connection.rb:34:in `block in with_lock' /var/www/discourse/vendor/bundle/ruby/3.1.0/gems/activesupport-7.0.4.1/lib/active_support/concurrency/load_interlock_aware_monitor.rb:25:in `handle_interrupt' /var/www/discourse/vendor/bundle/ruby/3.1.0/gems/activesupport-7.0.4.1/lib/active_support/concurrency/load_interlock_aware_monitor.rb:25:in `block in synchronize' /var/www/discourse/vendor/bundle/ruby/3.1.0/gems/activesupport-7.0.4.1/lib/active_support/concurrency/load_interlock_aware_monitor.rb:21:in `handle_interrupt' /var/www/discourse/vendor/bundle/ruby/3.1.0/gems/activesupport-7.0.4.1/lib/active_support/concurrency/load_interlock_aware_monitor.rb:21:in `synchronize' /var/www/discourse/vendor/bundle/ruby/3.1.0/gems/mini_sql-1.4.0/lib/mini_sql/active_record_postgres/connection.rb:34:in `with_lock' /var/www/discourse/vendor/bundle/ruby/3.1.0/gems/mini_sql-1.4.0/lib/mini_sql/active_record_postgres/connection.rb:38:in `run' /var/www/discourse/vendor/bundle/ruby/3.1.0/gems/mini_sql-1.4.0/lib/mini_sql/postgres/connection.rb:181:in `exec' /var/www/discourse/lib/tasks/posts.rake:383:in `block (3 levels) in
' /var/www/discourse/lib/tasks/posts.rake:366:in `each' /var/www/discourse/lib/tasks/posts.rake:366:in `block (2 levels) in
' /var/www/discourse/vendor/bundle/ruby/3.1.0/gems/activerecord-7.0.4.1/lib/active_record/connection_adapters/abstract/transaction.rb:319:in `block in within_new_transaction' /var/www/discourse/vendor/bundle/ruby/3.1.0/gems/activesupport-7.0.4.1/lib/active_support/concurrency/load_interlock_aware_monitor.rb:25:in `handle_interrupt' /var/www/discourse/vendor/bundle/ruby/3.1.0/gems/activesupport-7.0.4.1/lib/active_support/concurrency/load_interlock_aware_monitor.rb:25:in `block in synchronize' /var/www/discourse/vendor/bundle/ruby/3.1.0/gems/activesupport-7.0.4.1/lib/active_support/concurrency/load_interlock_aware_monitor.rb:21:in `handle_interrupt' /var/www/discourse/vendor/bundle/ruby/3.1.0/gems/activesupport-7.0.4.1/lib/active_support/concurrency/load_interlock_aware_monitor.rb:21:in `synchronize' /var/www/discourse/vendor/bundle/ruby/3.1.0/gems/activerecord-7.0.4.1/lib/active_record/connection_adapters/abstract/transaction.rb:317:in `within_new_transaction' /var/www/discourse/vendor/bundle/ruby/3.1.0/gems/activerecord-7.0.4.1/lib/active_record/connection_adapters/abstract/database_statements.rb:316:in `transaction' /var/www/discourse/vendor/bundle/ruby/3.1.0/gems/activerecord-7.0.4.1/lib/active_record/transactions.rb:209:in `transaction' /var/www/discourse/lib/tasks/posts.rake:329:in `block in
' /usr/local/bin/bundle:25:in `load' /usr/local/bin/bundle:25:in `
' Tasks: TOP => posts:reorder_posts (See full trace by running task with --trace) ``` Interessante notare che non vedo alcun post numerato 93 nell’argomento. Vedo 92 e 94. L’utente 1 sono io, ma i post 92 e 94 non sono miei. In precedenza ho diviso l’argomento, quindi forse il 93 si è spostato in un altro argomento, non lo so. --- _[View the full topic](https://meta.discourse.org/t/rake-posts-reorder-posts-gives-uniqueviolation-error/254098)._