Thats what I thought the PEAR DB package should do. But:

I have a standard install of postgres in ubuntu and use a superadmin 
user for development. Therefore I think the database is ok and the 
user has the correct permissions. But to be sure I'll double check this.

Sequences are created automatically by the DB package. If this doesn't 
happen for you then your db user doesn't have sufficient permissions, 
or something in your DB package is broken.

I confirmed this. After creating the sequences all history entries 
where generated correctly.

This error better belong to the postgresql install files.

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]

                                 )



                         )



....

There are no history entries generated in kronolith with the Groupware 
1.0RC1 release.

In the sql driver of kronolith the $history-log() lines all return a 
unnoticed PEAR error complaining about an invalid SQL statement:



Beim Hinzufügen des Termins ist ein Fehler aufgetreten: DB Error: 
unknown error : INSERT INTO horde_histories (history_id, object_uid, 
history_ts, history_who, history_desc, history_action, history_extra) 
VALUES ('Object', 
'kronolith:xxxxxx:20060905011843.5fjjnst0l8ws@xxxxxxx, 1157411923, 
'markusw', NULL, 'add', NULL) [nativecode=FEHLER: ungültige 
Eingabesyntax für ganze Zahl: »Object«].



This is tested with horde running on a postgresql backend.

Currently I don't understand the history code completly, otherwise I 
would append a patch. I'll attach it when I've worked throught the code.