Hi!

Steven Davidson wrote:
> I understand that the /exact/ operator is relying on the (case
> insensitive by default) MySQL DB collation and I'm happy with this. It
> also seems to be relying on the DB's comparison engine (which IMHO
> appears broken in MySQL). I would say the behaviour of
> /iexact/ certainly looks inconsistent as it is *more* exact than
> /exact/ but on balance it appears that /exact/ is not doing the right
> thing here?

If you want space to take part in comparison, use char fields instead of
varchar. See: http://dev.mysql.com/doc/refman/5.0/en/char.html

-- 
Dmitry Dulepov
Twitter: http://twitter.com/dmitryd/
Web: http://dmitry-dulepov.com/

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-us...@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Reply via email to