The Schema module http://drupal.org/project/schema is reporting a mismatch on the ldapauth module's tables. (using Drupal 6.16)

Mismatch (1)
Tables for which the schema and database are different.
ldapauth

*
ldapauth
o ldapdata_binddn: unexpected column in database
o ldapdata_bindpw: unexpected column in database
o ldapdata_rwattrs: unexpected column in database
o ldapdata_roattrs: unexpected column in database
o ldapdata_mappings: unexpected column in database
o ldapdata_attrs: unexpected column in database
o ldapdata_filter_php: unexpected column in database
o ldapgroups_in_dn: unexpected column in database
o ldapgroups_dn_attribute: unexpected column in database
o ldapgroups_attr: unexpected column in database
o ldapgroups_in_attr: unexpected column in database
o ldapgroups_as_entries: unexpected column in database
o ldapgroups_entries: unexpected column in database
o ldapgroups_entries_attribute: unexpected column in database
o ldapgroups_mappings: unexpected column in database
o ldapgroups_mappings_filter: unexpected column in database
o ldapgroups_filter_php: unexpected column in database
o ldapgroups_groups: unexpected column in database

CommentFileSizeAuthor
#6 ldapauth_schema_fix.patch4.06 KBmasondib

Comments

lambic’s picture

Those columns are added by the ldapgroups and ldapdata modules so they're not part of the original schema. Maybe the table should be created with all columns to begin with, even if the extra ones end up being unused.

verta’s picture

Perhaps the patch in #775182: Add description of database will address this?

Apologies for possible duplicate with #651192: ldap group => drupal roles and schema errors.

lambic’s picture

No, that patch only adds descriptions for the baseline ldapauth columns, it doesn't have the ldapgroups or ldapdata columns listed at all.

verta’s picture

+1 for the idea in #1!

Maybe the table should be created with all columns to begin with, even if the extra ones end up being unused.

masondib’s picture

Status: Active » Needs review

I was able to fix this on my system using a call to hook_schema_alter() in the ldapdata.install and ldapgroups.install files, which I've rolled into a patch against the 6.x-1.0-beta2 version. If you apply the attached patch from the ldap_integration root directory it should stop Schema from yelling at you. Testing appreciated.

EDIT -- Sorry, forgot the patch! Attached in comment #6.

masondib’s picture

StatusFileSize
new4.06 KB

Here's the patch.

cgmonroe’s picture

Version: 6.x-1.0-beta2 » 6.x-1.x-dev
Status: Needs review » Fixed

FYI - This is fixed in the dev version... when import/export and features support added.

Status: Fixed » Closed (fixed)

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