You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm following this guide to install Discourse locally for testing and development.
When running the migrations according to the instructions (RAILS_ENV=test bundle exec rake db:create db:migrate), it breaks:
== 20190429180007 AddAnnotatorStoreTagNames: migrating ========================
-- create_table(:annotator_store_tag_names, {})
rake aborted!
StandardError: An error has occurred, this and all later migrations canceled:
PG::DuplicateTable: ERROR: relation "annotator_store_tag_names" already exists
The text was updated successfully, but these errors were encountered:
I did yes, although I do remember there being some fiddling with the annotator-store gem (although I believe it was a different issue than the one you've posted)
That's a real weird error because the table name referenced only appears once in the migrations, so not sure why it would exist already; you might try a rake db:drop db:create to see if running the migrations from scratch helps.
Failing that, putting a check in the migration like
create_table : annotator_store_tag_names do |t|
...
end unless ActiveRecord::Base.connection.table_exists?('annotator_store_tag_names')
This is now resolved. Renaming the "annotator_store-gem" to "discourse-annotator" required namespace changes (that were used in migrations) as well as renaming all tables. So it made sense to replace all previous migrations with just one.
I'm following this guide to install Discourse locally for testing and development.
When running the migrations according to the instructions (
RAILS_ENV=test bundle exec rake db:create db:migrate
), it breaks:The text was updated successfully, but these errors were encountered: