1.1 --- a/update/core-update.v3.0.0-v3.0.1.sql	Wed Mar 26 20:08:50 2014 +0100
     1.2 +++ b/update/core-update.v3.0.0-v3.0.1.sql	Sat Apr 05 23:04:43 2014 +0200
     1.3 @@ -1,9 +1,21 @@
     1.4 +-- NOTICE: This update script disables the "no_reserve_beat_path" setting for
     1.5 +--         all policies. If this is not intended, please edit this script
     1.6 +--         before applying it to your database.
     1.7 +
     1.8  BEGIN;
     1.9  
    1.10  CREATE OR REPLACE VIEW "liquid_feedback_version" AS
    1.11    SELECT * FROM (VALUES ('3.0.1', 3, 0, 1))
    1.12    AS "subquery"("string", "major", "minor", "revision");
    1.13  
    1.14 +ALTER TABLE "policy" ALTER COLUMN "no_reverse_beat_path" SET DEFAULT FALSE;
    1.15 +
    1.16 +UPDATE "policy" SET "no_reverse_beat_path" = FALSE;  -- recommended
    1.17 +
    1.18 +COMMENT ON COLUMN "policy"."no_reverse_beat_path" IS 'EXPERIMENTAL FEATURE: Causes initiatives with "reverse_beat_path" flag to not be "eligible", thus disallowing them to be winner. See comment on column "initiative"."reverse_beat_path". This option ensures both that a winning initiative is never tied in a (weak) condorcet paradox with the status quo and a winning initiative always beats the status quo directly with a simple majority.';
    1.19 +
    1.20 +COMMENT ON COLUMN "policy"."no_multistage_majority" IS 'EXPERIMENTAL FEATURE: Causes initiatives with "multistage_majority" flag to not be "eligible", thus disallowing them to be winner. See comment on column "initiative"."multistage_majority". This disqualifies initiatives which could cause an instable result. An instable result in this meaning is a result such that repeating the ballot with same preferences but with the winner of the first ballot as status quo would lead to a different winner in the second ballot. If there are no direct majorities required for the winner, or if in direct comparison only simple majorities are required and "no_reverse_beat_path" is true, then results are always stable and this flag does not have any effect on the winner (but still affects the "eligible" flag of an "initiative").';
    1.21 +
    1.22  ALTER TABLE "initiative" ADD COLUMN "first_preference_votes" INT4;
    1.23  
    1.24  ALTER TABLE "initiative" DROP CONSTRAINT "non_admitted_initiatives_cant_contain_voting_results";