liquid_feedback_core

changeset 419:eaba9174d117 v2.2.6

Marked "no_reverse_beat_path" and "no_multistage_majority" as experimental; Disabled "no_reverse_beat_path" by default
author jbe
date Sat Apr 05 22:50:58 2014 +0200 (2014-04-05)
parents 992ec266356d
children 044a2b65c707
files core.sql update/core-update.v2.2.5-v2.2.6.sql
line diff
     1.1 --- a/core.sql	Sun Aug 11 22:46:44 2013 +0200
     1.2 +++ b/core.sql	Sat Apr 05 22:50:58 2014 +0200
     1.3 @@ -7,7 +7,7 @@
     1.4  BEGIN;
     1.5  
     1.6  CREATE VIEW "liquid_feedback_version" AS
     1.7 -  SELECT * FROM (VALUES ('2.2.5', 2, 2, 5))
     1.8 +  SELECT * FROM (VALUES ('2.2.6', 2, 2, 6))
     1.9    AS "subquery"("string", "major", "minor", "revision");
    1.10  
    1.11  
    1.12 @@ -373,7 +373,7 @@
    1.13          "indirect_majority_strict"      BOOLEAN NOT NULL DEFAULT TRUE,
    1.14          "indirect_majority_positive"    INT4    NOT NULL DEFAULT 0,
    1.15          "indirect_majority_non_negative" INT4   NOT NULL DEFAULT 0,
    1.16 -        "no_reverse_beat_path"          BOOLEAN NOT NULL DEFAULT TRUE,
    1.17 +        "no_reverse_beat_path"          BOOLEAN NOT NULL DEFAULT FALSE,
    1.18          "no_multistage_majority"        BOOLEAN NOT NULL DEFAULT FALSE,
    1.19          CONSTRAINT "timing" CHECK (
    1.20            ( "polling" = FALSE AND
    1.21 @@ -413,8 +413,8 @@
    1.22  COMMENT ON COLUMN "policy"."indirect_majority_strict"       IS 'If TRUE, then the indirect majority must be strictly greater than "indirect_majority_num"/"indirect_majority_den", otherwise it may also be equal.';
    1.23  COMMENT ON COLUMN "policy"."indirect_majority_positive"     IS 'Absolute number of votes in favor of the winner neccessary in a beat path to the status quo for an initaitive to be attainable as winner';
    1.24  COMMENT ON COLUMN "policy"."indirect_majority_non_negative" IS 'Absolute number of sum of votes in favor and abstentions in a beat path to the status quo for an initiative to be attainable as winner';
    1.25 -COMMENT ON COLUMN "policy"."no_reverse_beat_path"  IS '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.26 -COMMENT ON COLUMN "policy"."no_multistage_majority" IS '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.27 +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.28 +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.29  
    1.30  
    1.31  CREATE TABLE "unit" (
     2.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
     2.2 +++ b/update/core-update.v2.2.5-v2.2.6.sql	Sat Apr 05 22:50:58 2014 +0200
     2.3 @@ -0,0 +1,19 @@
     2.4 +-- NOTICE: This update script disables the "no_reserve_beat_path" setting for
     2.5 +--         all policies. If this is not intended, please edit this script
     2.6 +--         before applying it to your database.
     2.7 +
     2.8 +BEGIN;
     2.9 +
    2.10 +CREATE OR REPLACE VIEW "liquid_feedback_version" AS
    2.11 +  SELECT * FROM (VALUES ('2.2.6', 2, 2, 6))
    2.12 +  AS "subquery"("string", "major", "minor", "revision");
    2.13 +
    2.14 +ALTER TABLE "policy" ALTER COLUMN "no_reverse_beat_path" SET DEFAULT FALSE;
    2.15 +
    2.16 +UPDATE "policy" SET "no_reverse_beat_path" = FALSE;  -- recommended
    2.17 +
    2.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.';
    2.19 +
    2.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").';
    2.21 +
    2.22 +COMMIT;

Impressum / About Us