[Tickets #4381] Kronolith History in Groupware broken

bugs@bugs.horde.org bugs at bugs.horde.org
Mon Sep 4 16:33:40 PDT 2006


DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/?id=4381
-----------------------------------------------------------------------
 Ticket             | 4381
 Updated By         | markus at emedia-solutions-wolf.de
 Summary            | Kronolith History in Groupware broken
 Queue              | Horde Framework Packages
 Version            | FRAMEWORK_3
 Type               | Bug
 State              | Unconfirmed
 Priority           | 1. Low
 Owners             | 
-----------------------------------------------------------------------


markus at emedia-solutions-wolf.de (2006-09-04 16:33) wrote:

This bug may be related to missing postgresql sequences not generated
automatically on installation.
When echoing the $values variable in the history#log() method I'll get the
following output:

Array
(
    [0] => DB_Error Object
        (
            [error_message_prefix] => 
            [mode] => 1
            [level] => 1024
            [code] => -1
            [message] => DB Error: unknown error
            [userinfo] => SELECT NEXTVAL('horde_histories_seq')
[nativecode=FEHLER:  Relation »horde_histories_seq« existiert nicht]
            [backtrace] => Array
                (
                    [0] => Array
                        (
                            [file] =>
/home/markusw/Desktop/horde/pear/DB.php
                            [line] => 888
                            [function] => PEAR_Error
                            [class] => PEAR_Error
                            [object] => DB_Error Object
 *RECURSION*
                            [type] => ->
                            [args] => Array
                                (
                                    [0] => DB Error: unknown error
                                    [1] => -1
                                    [2] => 1
                                    [3] => 1024
                                    [4] => SELECT
NEXTVAL('horde_histories_seq') [nativecode=FEHLER:  Relation
»horde_histories_seq« existiert nicht]
                                )

                        )

....




More information about the bugs mailing list