liquid_feedback_core

diff update/core-update.v2.2.5-v2.2.6.sql @ 400:782eb17c7ad9

find changesets by author, revision, files, or words in the commit message
Remove referential integrity from "issue_order" table to avoid performance/locking issues
author jbe
date Sat Oct 12 15:33:35 2013 +0200 (2013-10-12)
parents 806561cce3b1
children f7b4457cf1a6
line diff
     1.1 --- a/update/core-update.v2.2.5-v2.2.6.sql	Fri Oct 11 20:50:16 2013 +0200
     1.2 +++ b/update/core-update.v2.2.5-v2.2.6.sql	Sat Oct 12 15:33:35 2013 +0200
     1.3 @@ -5,12 +5,13 @@
     1.4    AS "subquery"("string", "major", "minor", "revision");
     1.5  
     1.6  CREATE TABLE "issue_order" (
     1.7 -        "id"                    INT8            PRIMARY KEY REFERENCES "issue" ("id") ON DELETE CASCADE ON UPDATE CASCADE,
     1.8 +        "id"                    INT8            PRIMARY KEY, --REFERENCES "issue" ("id") ON DELETE CASCADE ON UPDATE CASCADE,
     1.9          "order_in_admission_state" INT4,
    1.10          "order_in_open_states"  INT4 );
    1.11  
    1.12  COMMENT ON TABLE "issue_order" IS 'Ordering information for issues that are not stored in the "issue" table to avoid locking of multiple issues at once';
    1.13  
    1.14 +COMMENT ON COLUMN "issue_order"."id"                       IS 'References "issue" ("id") but has no referential integrity trigger associated, due to performance/locking issues';
    1.15  COMMENT ON COLUMN "issue_order"."order_in_admission_state" IS 'To be used for sorting issues within an area, when showing only issues in admission state; NULL values sort last; updated by "lf_update_issue_order"';
    1.16  COMMENT ON COLUMN "issue_order"."order_in_open_states"     IS 'To be used for sorting issues within an area, when showing all open issues; NULL values sort last; updated by "lf_update_issue_order"';
    1.17

Impressum / About Us