liquid_feedback_core

view README @ 10:effdd7a04ea7

Version beta11

Support is now automatically deleted, when interest is deleted

All tables dealing with delegations now contain a column scope (including table delegation)

Changes in fields related to notify_email of member

Policies can now specify larger majorities to be reached (e.g. 2/3)

New column agreed in table initiative to mark, if initiative has reached majority specified by policy

Minor bugfix in constraint non_admitted_initiatives_cant_contain_voting_results of initiative table

Function delete_private_data() no longer deletes invite codes, which have been already used

Removed view battle_participant

Added index on opinion (member_id, initiative_id)
author jbe
date Fri Dec 25 12:00:00 2009 +0100 (2009-12-25)
parents e6faf5ff83af
children 92fc60ed705d
line source
2 Setup the database:
3 $ createdb liquid_feedback
4 $ psql -v ON_ERROR_STOP=1 -f core.sql liquid_feedback
6 Optionally insert demo data:
7 $ psql -v ON_ERROR_STOP=1 -f demo.sql liquid_feedback
9 Compile lf_update binary:
10 $ make
12 If you wish, copy the created lf_update file to /usr/local/bin or a
13 similar directory. Ensure that "lf_update dbname=liquid_feedback"
14 is called regularly. On successful run, lf_update will not produce
15 any output and exit with code 0.
17 NOTE: When writing to the database, some INSERTs must be executed
18 within the same transaction, e.g. issues can't exist without
19 an initiative and vice versa.
21 To create an export file, which is containing all but private data,
22 you may use the lf_export shell-script:
23 $ lf_export liquid_feedback export.sql.gz
25 To uninstall the software, delete the lf_update binary
26 and drop the database by entering the following command:
27 $ dropdb liquid_feedback

Impressum / About Us