https://bugzilla.wikimedia.org/show_bug.cgi?id=63500

            Bug ID: 63500
           Summary: Flow: broken flow table on beta labs
           Product: Wikimedia Labs
           Version: unspecified
          Hardware: All
               URL: http://en.wikipedia.beta.wmflabs.org/wiki/Talk:Flow_QA
                OS: All
            Status: NEW
          Severity: normal
          Priority: Unprioritized
         Component: deployment-prep (beta)
          Assignee: wikibugs-l@lists.wikimedia.org
          Reporter: sp...@wikimedia.org
                CC: benap...@gmail.com, cmcma...@wikimedia.org,
                    g...@wikimedia.org, has...@free.fr,
                    mhershber...@wikimedia.org, platoni...@gmail.com
       Web browser: ---
   Mobile Platform: ---

Gerrit 122865 added a maintenance script
(db_patches/patch-add_workflow_type.sql) that did too much, dropping the DB
column `flow_workflow.workflow_definition_id` prematurely. We fixed the script
in gerrit 123501 but beta labs somehow ran the buggy version, and now the
column is gone causing
  Unknown column 'workflow_definition_id' in 'where clause'

There are three ways to fix this on beta labs:

a) Manually add back the DB column the buggy maintenance script dropped. We've
already gone through the steps on our labs instance.
b) Drop all the Flow tables and let maintenance scripts re-add them.
c) Write a smart maintenance script that figures out if the column was dropped
and adds it back.

a) or b) is quick but will require beta labs DB access by the Flow team... how?

c) we can do on our own, but it's tricky because as I understand it, we really
do want to drop that column, but not until gerrit 115576. So the maintenance
script has to be smart about whether it applies.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
_______________________________________________
Wikibugs-l mailing list
Wikibugs-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l

Reply via email to