MySQL doesn't like "unique=True" on TextFields

micahmanquen / django-ldap-groups

Automatically exported from code.google.com/p/django-ldap-groups

0 stars 0 forks source link

MySQL doesn't like "unique=True" on TextFields #1

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago

Hi! This project looks very promising! Just a quick note on your LDAPGroup
model: the org_unit is currently a TextField and unique=True. MySQL can't
index this and Django currently offers no workaround (see
http://code.djangoproject.com/ticket/2495 for details). The upper limit for
indexes on CharFields is 255 charactes. I'm no LDAP/AD expert, so I don't
really know if that would suffice for OUs...

Original issue reported on code.google.com by piquad...@gmail.com on 1 Sep 2009 at 8:37

GoogleCodeExporter commented 8 years ago

Yes, this is a problem with Oracle also.  I'm inclined to remove the 
unique=True and 
leave it as a text field, as OUs can get very long, at least at my place of 
work.

Original comment by tphern...@gmail.com on 19 Jan 2010 at 9:16

GoogleCodeExporter commented 8 years ago

Fixed in latest version, I dropped the unique constraint.

Original comment by tphern...@gmail.com on 19 Jan 2010 at 10:41

Changed state: Fixed

GoogleCodeExporter commented 8 years ago

Issue 9 has been merged into this issue.

Original comment by tphern...@gmail.com on 20 Apr 2010 at 5:34