Table ldapauth Primary Key

lkeller - October 23, 2009 - 18:13
Project:LDAP integration
Version:6.x-1.0-alpha2
Component:Code
Category:bug report
Priority:normal
Assigned:miglius
Status:closed
Issue tags:ldapauth
Description

Although not certified by drupal.org have been working with Drupal in a MySQL Cluster, version mysql-cluster-gpl-7.0.7-linux-i686-glibc23, in a test environment. Found that table ldapauth created by module ldap_integration, once converted to the MySQL cluster engine, NDBCLUSTER, can not be dropped, reverted back to MyISAM or manipulated in any way. Found the problem to be the definition of the primary key and index. By default the field "sid" is auto_increment but has a non-unique index. Field "name" is the primary key. By redefining the auto-incrementing field "sid" as the primary key (as it should be) and placing a unique index on field "name" the table behaves as it should in the MySQL Cluster environment.

#1

miglius - October 27, 2009 - 14:31
Assigned to:Anonymous» miglius
Status:active» fixed

Thanks for spotting this. I have committed a fix to the cvs.

#2

System Message - November 10, 2009 - 14:40
Status:fixed» closed

Automatically closed -- issue fixed for 2 weeks with no activity.

 
 

Drupal is a registered trademark of Dries Buytaert.