Tickets :: Comment on [#14639] Primary key on all tables of horde database

Search Results: 39 of 129 [ <<First <Prev Next> Last>> ] [ Return to Search Results ]

* Your Email Address
* Spam protection	Enter the letters below: \ /.___..__.. .\ / >< \| \| \|\|\ \| >< / \ \| \|__\|\| \\|/ \
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!
Attachment
Watch this ticket

Saved Queries