I get the following error at the top of the modules screen when I attempt to enable the LDAP integration module:
user warning: You have an error in your SQL syntax. Check the manual that corresponds to your MySQL server version for the right syntax to use near '(1000) NOT NULL default '', user_attr varchar(255) NOT NULL query: CREATE TABLE ldapauth ( sid int NOT NULL auto_increment, name varchar(255) NOT NULL default '', status int NOT NULL default '0', server varchar(255) NOT NULL default '', port int(10) NOT NULL default '389', tls int NOT NULL default '0', encrypted int NOT NULL default '0', basedn text(1000) NOT NULL default '', user_attr varchar(255) NOT NULL default '', mail_attr VARCHAR(255) NOT NULL DEFAULT '', binddn varchar(255) NOT NULL default '', bindpw varchar(255) NOT NULL default '', bindpw_clear varchar(255) NOT NULL default '', ldap_groups_in_dn int NOT NULL default '0', ldap_groups_in_dn_desc int NOT NULL d in /path/to/drupal/includes/database.mysql.inc on line 172.
For what it's worth, I'm able to use the Drupal 4.7 version of the module, installed elsewhere on the same server, without any trouble. We're using MySQL version 4.0.21.
Comments
Comment #1
scafmac commentedThis should be fixed in the latest release.
Comment #2
jeff.k commentedI too am having issues. I am testing on a fresh install of Drupal 5 and am getting:
user warning: BLOB/TEXT column 'basedn' can't have a default value query: CREATE TABLE ldapauth ( sid int NOT NULL auto_increment, name varchar(255) NOT NULL default '', status int NOT NULL default '0', server varchar(255) NOT NULL default '', port int(10) NOT NULL default '389', tls int NOT NULL default '0', encrypted int NOT NULL default '0', basedn text(1000) NOT NULL default '', user_attr varchar(255) NOT NULL default '', mail_attr VARCHAR(255) NOT NULL DEFAULT '', binddn varchar(255) NOT NULL default '', bindpw varchar(255) NOT NULL default '', bindpw_clear varchar(255) NOT NULL default '', ldap_groups_in_dn int NOT NULL default '0', ldap_groups_in_dn_desc int NOT NULL default '0', ldap_group_dn_attribute varchar(255) default '', ldap_group_attr varchar(255) default '', ldap_groups_in_attr int NOT NULL default '0', ldap_groups_as_entries int NOT NULL default '0', ldap_group_entries varchar(255) default '', ldap_group_entries_attribute varchar(255) default '', ldapdata_binddn VARCHAR(255) NOT NULL default '', ldapdata_bindpw VARCHAR(255) NOT NULL default '', ldapdata_bindpw_clear VARCHAR(2) NOT NULL default '', ldapdata_rwattrs LONGTEXT NOT NULL default '', ldapdata_roattrs LONGTEXT NOT NULL default '', ldapdata_mappings LONGTEXT NOT NULL default '', PRIMARY KEY (name), KEY sid (sid) ) /*!40100 DEFAULT CHARACTER SET UTF8 */ in C:\server\htdocs\drupal\includes\database.mysql.inc on line 172.
Windows Server 2003
Apache
MySQL 5
Drupal 5
PHP 5
Comment #3
scafmac commentedIt is patched & available in HEAD. I'll make a new release this afternoon, but it will not be available. Sorry about that.
Comment #4
(not verified) commentedComment #5
Jean-Christophe commentedHi,
I still have the problem.
My setup is :
IIS 5 (on Windows Server 2000)
MySQL 5 (last stable version)
PHP 5 (last stable version)
Drupal 5 (last stable version)
LDAP Module (HEAD version)
I just made a fresh install. I still received
user warning: BLOB/TEXT column 'basedn' can't have a default value query: CREATE TABLE ldapauth ( sid int NOT NULL auto_increment, name varchar(255) NOT NULL default '', status int NOT NULL default '0', server varchar(255) NOT NULL default '', port int(10) NOT NULL default '389', tls int NOT NULL default '0', encrypted int NOT NULL default '0', basedn text(1000) NOT NULL default '', user_attr varchar(255) NOT NULL default '', mail_attr VARCHAR(255) NOT NULL DEFAULT '', binddn varchar(255) NOT NULL default '', bindpw varchar(255) NOT NULL default '', bindpw_clear varchar(255) NOT NULL default '', PRIMARY KEY (name), KEY sid (sid) ) /*!40100 DEFAULT CHARACTER SET UTF8 */ in C:\Inetpub\wwwroot\includes\database.mysql.inc on line 172.Exept this installation problem, Drupal works fine.
Can I provide more info to help ?
Comment #6
scafmac commentedLooks like it got lost from HEAD. I'll make a commit to the 1.2 branch soon.
Comment #7
kreaper commentedIt got lost when I was creating individual install files for each module.
The problem with this particular issue is described here
http://bugs.mysql.com/bug.php?id=25520
Incorporated the changes to HEAD. Will be comitting soon.
Comment #8
kreaper commentedbug fix committed to HEAD. Will be incorporated into future releases
Comment #9
Jean-Christophe commentedI confirm, Thanks a lot!
Comment #10
(not verified) commented