liquid_feedback_core
diff core.sql @ 420:044a2b65c707
Merged from 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 23:04:43 2014 +0200 (2014-04-05) |
parents | db9ccf3c05f4 eaba9174d117 |
children | 73c2ab2d068f |
line diff
1.1 --- a/core.sql Wed Mar 26 20:08:50 2014 +0100 1.2 +++ b/core.sql Sat Apr 05 23:04:43 2014 +0200 1.3 @@ -373,7 +373,7 @@ 1.4 "indirect_majority_strict" BOOLEAN NOT NULL DEFAULT TRUE, 1.5 "indirect_majority_positive" INT4 NOT NULL DEFAULT 0, 1.6 "indirect_majority_non_negative" INT4 NOT NULL DEFAULT 0, 1.7 - "no_reverse_beat_path" BOOLEAN NOT NULL DEFAULT TRUE, 1.8 + "no_reverse_beat_path" BOOLEAN NOT NULL DEFAULT FALSE, 1.9 "no_multistage_majority" BOOLEAN NOT NULL DEFAULT FALSE, 1.10 CONSTRAINT "timing" CHECK ( 1.11 ( "polling" = FALSE AND 1.12 @@ -413,8 +413,8 @@ 1.13 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.14 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.15 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.16 -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.17 -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.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 +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.20 1.21 1.22 CREATE TABLE "unit" (