Changes have been made in Git for this ticket:

Bug: 10443 fix another erroneous autoincrementKey change.
Also, 3 and 7 migration were essentially duplicates (7 was to fix an 
error in the 3
migration that has since been fixed in 3). make the 7 migration a noop.

  2 files changed, 9 insertions(+), 88 deletions(-)
http://git.horde.org/horde-git/-/commit/9df7438cc5e57e34d327b498bd98ed3674b58652

Changes have been made in Git for this ticket:

Bug: 10443 - fix erroneous primaryKey -> autoincrementKey change
Tables seem to have be created correctly with the incorrect usage in
MySQL and Postgres 9, plus all existing content tests were passing. This
just fixes the migrations for new installs.

  1 files changed, 7 insertions(+), 3 deletions(-)
http://git.horde.org/horde-git/-/commit/a233e45407e62132de5653e14146697b54ec5590

There are more wrong usages, in content:
rampage_tagged and rampage_user_tag_stats use it for multi-column keys
rampage_tag_stats is using it for tag_id, which is never 
autoincremented, but always inserted manually.

ansel_hashes.style_hash is defined as an autoincrementKey and string 
column at the same time, which are incompatible.