liquid_feedback_core
annotate README @ 113:76ffbafb23b5
Work on event and notification system; Added more "issue_state"s; Replaced "ignored_issue" table; Removal of sessions in "delete_member" function
- "state" column of table "event" is now always filled
- splitted revocation state into 3 new "issue_state"s:
- 'canceled_revoked_before_accepted'
- 'canceled_after_revocation_during_discussion'
- 'canceled_after_revocation_during_verification'
- Added columns "notify_level" and "notify_event_id" to "member" table
- Replaced view "ignored_issue" by three new views:
- TABLE "ignored_member"
- TABLE "ignored_initiative"
- TABLE "non_voter"
- Function "delete_member" now removes "session"s
- Added member specific views on events:
- VIEW "event_seen_by_member"
- VIEW "pending_notification"
- "state" column of table "event" is now always filled
- splitted revocation state into 3 new "issue_state"s:
- 'canceled_revoked_before_accepted'
- 'canceled_after_revocation_during_discussion'
- 'canceled_after_revocation_during_verification'
- Added columns "notify_level" and "notify_event_id" to "member" table
- Replaced view "ignored_issue" by three new views:
- TABLE "ignored_member"
- TABLE "ignored_initiative"
- TABLE "non_voter"
- Function "delete_member" now removes "session"s
- Added member specific views on events:
- VIEW "event_seen_by_member"
- VIEW "pending_notification"
author | jbe |
---|---|
date | Sat Mar 05 22:05:13 2011 +0100 (2011-03-05) |
parents | e6faf5ff83af |
children | 92fc60ed705d |
rev | line source |
---|---|
jbe@0 | 1 |
jbe@0 | 2 Setup the database: |
jbe@0 | 3 $ createdb liquid_feedback |
jbe@0 | 4 $ psql -v ON_ERROR_STOP=1 -f core.sql liquid_feedback |
jbe@0 | 5 |
jbe@0 | 6 Optionally insert demo data: |
jbe@0 | 7 $ psql -v ON_ERROR_STOP=1 -f demo.sql liquid_feedback |
jbe@0 | 8 |
jbe@0 | 9 Compile lf_update binary: |
jbe@0 | 10 $ make |
jbe@0 | 11 |
jbe@0 | 12 If you wish, copy the created lf_update file to /usr/local/bin or a |
jbe@0 | 13 similar directory. Ensure that "lf_update dbname=liquid_feedback" |
jbe@0 | 14 is called regularly. On successful run, lf_update will not produce |
jbe@0 | 15 any output and exit with code 0. |
jbe@0 | 16 |
jbe@0 | 17 NOTE: When writing to the database, some INSERTs must be executed |
jbe@0 | 18 within the same transaction, e.g. issues can't exist without |
jbe@0 | 19 an initiative and vice versa. |
jbe@0 | 20 |
jbe@8 | 21 To create an export file, which is containing all but private data, |
jbe@8 | 22 you may use the lf_export shell-script: |
jbe@8 | 23 $ lf_export liquid_feedback export.sql.gz |
jbe@8 | 24 |
jbe@0 | 25 To uninstall the software, delete the lf_update binary |
jbe@0 | 26 and drop the database by entering the following command: |
jbe@0 | 27 $ dropdb liquid_feedback |
jbe@0 | 28 |