[Tickets #9835] db schema update for h3->h4 converstion

bugs at horde.org bugs at horde.org
Thu Apr 7 15:49:07 UTC 2011


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

Ticket URL: http://bugs.horde.org/ticket/9835
------------------------------------------------------------------------------
  Ticket             | 9835
  Created By         | dan at soleks.com
  Summary            | db schema update for h3->h4 converstion
  Queue              | Horde Base
  Version            | 4.0
  Type               | Bug
  State              | Unconfirmed
  Priority           | 2. Medium
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


dan at soleks.com (2011-04-07 15:49) wrote:

when i did db schema conversion as part of h3->h4 upgrade i got the following:

SQLSTATE[42P16]: Invalid table definition: 7 ERROR: multiple primary  
keys for table "imp_sentmail" are not allowed
SQLSTATE[42P16]: Invalid table definition: 7 ERROR: multiple primary  
keys for table "ingo_rules" are not allowed
SQLSTATE[42P16]: Invalid table definition: 7 ERROR: multiple primary  
keys for table "turba_shares" are not allowed
SQLSTATE[42P16]: Invalid table definition: 7 ERROR: multiple primary  
keys for table "kronolith_shares" are not allowed
SQLSTATE[42P16]: Invalid table definition: 7 ERROR: multiple primary  
keys for table "nag_shares" are not allowed
SQLSTATE[42P16]: Invalid table definition: 7 ERROR: multiple primary  
keys for table "mnemo_shares" are not allowed
SQLSTATE[42P16]: Invalid table definition: 7 ERROR: multiple primary  
keys for table "horde_groups" are not allowed
SQLSTATE[42P16]: Invalid table definition: 7 ERROR: multiple primary  
keys for table "horde_histories" are not allowed
SQLSTATE[42P16]: Invalid table definition: 7 ERROR: multiple primary  
keys for table "horde_perms" are not allowed
SQLSTATE[42P16]: Invalid table definition: 7 ERROR: multiple primary  
keys for table "horde_vfs" are not allowed

database backend is postgres






More information about the bugs mailing list