Hi blizzz, you'll find following the structure before and after the
attempt (current).
CREATE TABLE `oc_ldap_user_mapping` (
`ldap_dn` varchar(255) NOT NULL DEFAULT '',
`owncloud_name` varchar(255) NOT NULL DEFAULT '',
`directory_uuid` varchar(255) NOT NULL DEFAULT '',
UNIQUE KEY `ldap_dn_users` (`ldap_dn`),
UNIQUE KEY `owncloud_name_users` (`owncloud_name`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;
Current table structure
CREATE TABLE `oc_ldap_user_mapping` (
`ldap_dn` varchar(255) COLLATE utf8_bin NOT NULL DEFAULT '',
`owncloud_name` varchar(255) COLLATE utf8_bin NOT NULL DEFAULT '',
`directory_uuid` varchar(255) COLLATE utf8_bin NOT NULL DEFAULT '',
UNIQUE KEY `ldap_dn_users` (`ldap_dn`),
UNIQUE KEY `owncloud_name_users` (`owncloud_name`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_bin;
Regards.
Mathias
On 06/08/2014 15:59, blizzz wrote:
do you still have the old table somewhere available? could you give us
the structure before the migration? The SQL command would be
```sql
DESCRIBE oc_ldap_user_mapping;
```
---
Reply to this email directly or view it on GitHub:
https://github.com/owncloud/core/issues/9893#issuecomment-51322625
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
