Opened 4 years ago

Closed 4 years ago

#2283 closed bug (duplicate)

failing migrations on the developer database dump

Reported by: lantti Owned by:
Priority: minor Milestone: unassigned
Component: FrameWork Keywords:


Some of the wordcodes that should be added by running migrations are already present in the words.sql database dump. This causes the migrations to fail. The workaround that I used to continue with my install was replacing the INSERT INTO queries in the tools/roxmigration/roxmigration.php/_writeWordCodeToDb() function with REPLACE INTO queries. This way the query succeeds even if there is already an identical wordcode in the database.

Should we make this change to the official code too? Is there a reason why we would like to have a fatal error instead of silent replacement in such a conflict between the existing wordcode and a migration? Or would it be better to fix the developer db dump instead?

Change History (1)

comment:1 Changed 4 years ago by lantti

  • Resolution set to duplicate
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.