liquid_feedback_core

changeset 417:bc94ea65757b

Reconstruct battle data in update script to avoid future data loss when executing "clean_issue" to delete voting data
author jbe
date Wed Mar 26 17:09:55 2014 +0100 (2014-03-26)
parents db9ccf3c05f4
children 1088d83d92e8
files update/core-update.v3.0.0-v3.0.1.sql
line diff
     1.1 --- a/update/core-update.v3.0.0-v3.0.1.sql	Wed Mar 26 14:45:49 2014 +0100
     1.2 +++ b/update/core-update.v3.0.0-v3.0.1.sql	Wed Mar 26 17:09:55 2014 +0100
     1.3 @@ -71,6 +71,26 @@
     1.4    WHERE "initiative"."admitted"
     1.5    AND "initiative"."id" = "subquery"."initiative_id";
     1.6  
     1.7 +-- reconstruct battle data to avoid future data loss when
     1.8 +-- executing "clean_issue" to delete voting data:
     1.9 +INSERT INTO "battle" (
    1.10 +    "issue_id",
    1.11 +    "winning_initiative_id",
    1.12 +    "losing_initiative_id",
    1.13 +    "count"
    1.14 +  ) SELECT
    1.15 +    "battle_view"."issue_id",
    1.16 +    "battle_view"."winning_initiative_id",
    1.17 +    "battle_view"."losing_initiative_id",
    1.18 +    "battle_view"."count"
    1.19 +  FROM "battle_view"
    1.20 +  LEFT JOIN "battle"
    1.21 +  ON "battle_view"."winning_initiative_id" = "battle"."winning_initiative_id"
    1.22 +  AND "battle_view"."losing_initiative_id" = "battle"."losing_initiative_id"
    1.23 +  -- NOTE: comparisons with status-quo are intentionally omitted to mark
    1.24 +  --       issues that were counted prior LiquidFeedback Core v2.0.0
    1.25 +  WHERE "battle" ISNULL;
    1.26 +
    1.27  CREATE OR REPLACE FUNCTION "close_voting"("issue_id_p" "issue"."id"%TYPE)
    1.28    RETURNS VOID
    1.29    LANGUAGE 'plpgsql' VOLATILE AS $$

Impressum / About Us