[lqfb-main] Errors on lf_update

[Stratos Zolotas]

Forgive my ignorance, how to remove o member from the database?

On Mon, May 14, 2012 at 3:56 PM, Stratos Zolotas <strzol at gmail.com> wrote:

> Thanks!
>
> I have already tried solution B but it fails when i try to restore tmp.sql
> (i don't remember the specific error, but i tried it more than once). I had
> to restore the whole database again.
>
> I will try solution C and report again, if there is any issue.
>
>
> Thanks again.
>
>
> On Mon, May 14, 2012 at 3:50 PM, Jan Behrens <
> jbe at public-software-group.org> wrote:
>
>> On 05/13/12 19:50, Stratos Zolotas wrote:
>>
>>> Hello to all.
>>>
>>> After upgrading to 2.0.8 core i'm getting the following messases on
>>> syslog by the lf_update.
>>>
>>> <mailto:main at dev.**liquidfeedback.org <main at dev.liquidfeedback.org>>May
>>> 13 20:46:53 barbarossa
>>>
>>> lf_updated: Error while calling SQL function "check_issue"(...):
>>> May 13 20:46:53 barbarossa lf_updated: ERROR:  null value in column
>>> "winning_initiative_id" violates not-null constraint
>>> May 13 20:46:53 barbarossa lf_updated: CONTEXT:  SQL statement "INSERT
>>> INTO "battle" ( "issue_id", "winning_initiative_id",
>>> "losing_initiative_id", "count" ) SELECT "issue_id",
>>> "winning_initiative_id", "losing_initiative_id", "count" FROM
>>> "battle_view" WHERE "issue_id" =  $1 "
>>> May 13 20:46:53 barbarossa lf_updated: PL/pgSQL function "close_voting"
>>> line 46 at SQL statement
>>> May 13 20:46:53 barbarossa lf_updated: SQL statement "SELECT
>>> "close_voting"( $1 )"
>>> May 13 20:46:53 barbarossa lf_updated: PL/pgSQL function "check_issue"
>>> line 118 at PERFORM
>>> May 13 20:46:53 barbarossa lf_updated: Error while calling SQL function
>>> "check_issue"(...):
>>> May 13 20:46:53 barbarossa lf_updated: ERROR:  null value in column
>>> "losing_initiative_id" violates not-null constraint
>>> May 13 20:46:53 barbarossa lf_updated: CONTEXT:  SQL statement "INSERT
>>> INTO "battle" ( "issue_id", "winning_initiative_id",
>>> "losing_initiative_id", "count" ) SELECT "issue_id",
>>> "winning_initiative_id", "losing_initiative_id", "count" FROM
>>> "battle_view" WHERE "issue_id" =  $1 "
>>> May 13 20:46:53 barbarossa lf_updated: PL/pgSQL function "close_voting"
>>> line 46 at SQL statement
>>> May 13 20:46:53 barbarossa lf_updated: SQL statement "SELECT
>>> "close_voting"( $1 )"
>>> May 13 20:46:53 barbarossa lf_updated: PL/pgSQL function "check_issue"
>>> line 118 at PERFORM
>>>
>>> Is this something to worry about?
>>>
>>
>> Yes, it is :-)  It will cause lf_update to fail when counting votes.
>>
>> It turned out to be a bug in core-update.v1.4.0-v2.0.0.sql. I have fixed
>> it in our repository, and we'll make a new release of the
>> LiquidFeedback-Core soon.
>>
>> You may solve the problem in one of the following ways:
>>
>>
>> SOLUTION A)
>>
>> Wait till LiquidFeedback Core v2.0.9 is released and update to v2.0.9.
>>
>>
>> alternative SOLUTION B)
>>
>> Follow the instructions regarding updating in the README file:
>>
>> ======
>> Updating is done using the update scripts in the update/ directory.
>> After updating it is recommended to recreate the schema as follows:
>>
>> pg_dump --disable-triggers --data-only DATABASE_NAME > tmp.sql
>> dropdb DATABASE_NAME
>> createdb DATABASE_NAME
>> psql -v ON_ERROR_STOP=1 -f core.sql DATABASE_NAME
>> psql -v ON_ERROR_STOP=1 -f tmp.sql DATABASE_NAME
>> rm tmp.sql
>> ======
>>
>> If you re-recreate the schema (which is recommended in any case), the
>> problem will be solved automatically.
>>
>>
>> alternative SOLUTION C)
>>
>> Enter the following commands into your database:
>>
>> ALTER TABLE "battle" ALTER COLUMN "winning_initiative_id" DROP NOT NULL;
>> ALTER TABLE "battle" ALTER COLUMN "losing_initiative_id" DROP NOT NULL;
>>
>>
>> If you have further queestions, feel free to ask. Thank you for helping
>> us to notice the bug.
>>
>>
>> Regards
>> Jan Behrens
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://dev.liquidfeedback.org/pipermail/main/attachments/20120517/104e7495/attachment.html>