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

bugs at horde.org bugs at horde.org
Thu Jun 30 10:09:12 UTC 2011


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

Ticket URL: http://bugs.horde.org/ticket/9835
------------------------------------------------------------------------------
  Ticket             | 9835
  Updated By         | Jan Schneider <jan at horde.org>
  Summary            | db schema update for h3->h4 converstion
  Queue              | Horde Base
  Version            | 4.0
  Type               | Bug
-State              | No Feedback
+State              | Feedback
  Priority           | 2. Medium
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


Jan Schneider <jan at horde.org> (2011-06-30 10:09) wrote:

> The reason it happens on my system, is that the primary key constraints have
> different names than those that the upgrade script is expecting. It  
> attempts to
> drop the primary key using an incorrect name which fails, then adds it back
> again. The add of course fails with the reported message.

So, the question is why? The default names for primary key constraints  
in PostgreSQL are table_pkey. Why are yours table_idx?






More information about the bugs mailing list