6.0.0-git
2018-12-16

[#14639] Primary key on all tables of horde database
Summary Primary key on all tables of horde database
Queue Horde Groupware Webmail Edition
Queue Version 5.2.20
Type Bug
State Feedback
Priority 1. Low
Owners
Requester limperis (at) cti (dot) gr
Created 2017-05-10 (585 days ago)
Due
Updated 2017-05-16 (579 days ago)
Assigned 2017-05-10 (585 days ago)
Resolved
Milestone
Patch No

History
2017-05-16 07:29:38 limperis (at) cti (dot) gr Comment #5 Reply to this comment

ok
I created the primary keys on all the tables that they did not exist 
and after that it became possible work on Galera Spin and Mysql Innodb 
cluster.

I think the development team might consider it for one of the next updates
2017-05-11 08:00:15 Jan Schneider Comment #4 Reply to this comment
It is not possible to deploy the horde database on a large scale 
implementation based on mysql cluster,  without primary  key on all 
tables!
This is plain out wrong, this done all the time. Correct is: you 
cannot deploy certain horde tables on a cluster when using a 
combination of InnoDB table, MariaDB, and Galera. Which is a 
completely different thing.
2017-05-11 03:32:44 limperis (at) cti (dot) gr Comment #3 Reply to this comment
This is the  list for tables without primary key.

  content_schema_info
  gollem_schema_info
  gollem_sharesng_groups
  gollem_sharesng_users
  horde_activesync_cache
  horde_activesync_device_users
  horde_activesync_mailmap
  horde_activesync_map
  horde_activesync_schema_info
  horde_alarm_schema_info
  horde_auth_schema_info
  horde_cache_schema_info
  horde_core_schema_info
  horde_dav_collections
  horde_dav_objects
  horde_dav_schema_info
  horde_group_schema_info
  horde_groups_members
  horde_history_schema_info
  horde_imap_client_message
  horde_imap_client_metadata
  horde_imap_client_schema_info
  horde_lock_schema_info
  horde_perms_schema_info
  horde_prefs_schema_info
  horde_queue_schema_info
  horde_service_weather_schema_info
  horde_sessionhandler_schema_info
  horde_syncml_anchors
  horde_syncml_map
  horde_syncml_schema_info
  horde_token_schema_info
  horde_vfs_schema_info
  imp_schema_info
  ingo_forwards
  ingo_lists
  ingo_schema_info
  ingo_sharesng_groups
  ingo_sharesng_users
  kronolith_schema_info
  kronolith_sharesng_groups
  kronolith_sharesng_users
  mnemo_schema_info
  mnemo_sharesng_groups
  mnemo_sharesng_users
  nag_schema_info
  nag_shares_groups
  nag_shares_users
  nag_sharesng_groups
  nag_sharesng_users
  schinfo_schema_info
  trean_schema_info
  turba_schema_info
  turba_sharesng_groups
  turba_sharesng_users
  whatsnew_schema_info
  wicked_schema_info

It is not possible to deploy the horde database on a large scale 
implementation based on mysql cluster,  without primary  key on all 
tables!
2017-05-10 16:08:44 Jan Schneider Comment #2
State ⇒ Feedback
Reply to this comment
This list is a bit strange, because none of the *_schema_info tables 
has a primary key, and there are lots of those, much more than in your 
list. Thus I assume that the list is incomplete. We would have decide 
on a case by case basis if adding primary keys would make sense though.
2017-05-10 13:29:04 limperis (at) cti (dot) gr Comment #1
Type ⇒ Bug
State ⇒ Unconfirmed
Priority ⇒ 1. Low
Summary ⇒ Primary key on all tables of horde database
Queue ⇒ Horde Groupware Webmail Edition
Milestone ⇒
Patch ⇒ No
Reply to this comment
Hello, Horde team

I try to deplo horde on Mysql Innodb cluster or Galera cluster, but 
these environments require primary key on all database tables. These 
are the database logs that describe the problem:

'Table horde_auth_schema_info does not have any PRIMARY KEY. This is 
not compatible with Group Replication'
'Table horde_cache_schema_info does not have any PRIMARY KEY. This is 
not compatible with Group Replication'
'Table horde_core_schema_info does not have any PRIMARY KEY. This is 
not compatible with Group Replication'
'Table horde_dav_schema_info does not have any PRIMARY KEY. This is 
not compatible with Group Replication'
'Table horde_group_schema_info does not have any PRIMARY KEY. This is 
not compatible with Group Replication'
'Table horde_groups_members does not have any PRIMARY KEY. This is not 
compatible with Group Replication'
'Table horde_history_schema_info does not have any PRIMARY KEY. This 
is not compatible with Group Replication'
'Table horde_imap_client_schema_info does not have any PRIMARY KEY. 
This is not compatible with Group Replication'
'Table horde_lock_schema_info does not have any PRIMARY KEY. This is 
not compatible with Group Replication'
'Table horde_perms_schema_info does not have any PRIMARY KEY. This is 
not compatible with Group Replication

Is it predicted to add primary key to all tables at some subsequent 
distribution of horde?

If I add a primary key to all the tables, do you think the Horde will 
work properly or will problems occur?

You can see for this requirement for example  in url:   
https://mariadb.com/kb/en/mariadb/mariadb-galera-cluster-known-limitations/

Thank you.
Antonis Limperis



Saved Queries