[Tickets #9711] Re: Postgresql autoincrement broken

[bugs at horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/9711
------------------------------------------------------------------------------
  Ticket             | 9711
  Updated By         | Michael Slusarz <slusarz at horde.org>
  Summary            | Postgresql autoincrement broken
  Queue              | Horde Framework Packages
  Version            | Git master
  Type               | Bug
-State              | Assigned
+State              | Feedback
  Priority           | 3. High
  Milestone          | 4.0
  Patch              |
  Owners             |
------------------------------------------------------------------------------


Michael Slusarz <slusarz at horde.org> (2011-03-24 20:57) wrote:

This seems to fix things for me (migration works for me now and  
autoincrementing work).  I just don't know if these are correct  
assumptions for primaryKey.

Two further thoughts:
1. According to the 'primaryKey' implementation in the Postgresql  
schema class, primaryKey is expected/required to be an autoincrement  
column.  If that is the case, we should really pick a different name  
(e.g. 'autoincrementKey') since non-autoincrement columns can also be  
primary keys.
2. 'primaryKey' (or 'autoincrementKey' or whatever) should be a  
defined constant.