#2422: unique_together on SQLite uses 'iexact' matching, I expected this to be
'exact'
-----------------------------------+----------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: adrian
Status: closed | Component: Admin interface
Version: | Resolution: invalid
Keywords: SQlite | Stage: Unreviewed
Has_patch: 0 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
-----------------------------------+----------------------------------------
Changes (by Simon G. <[EMAIL PROTECTED]>):
* keywords: => SQlite
* status: reopened => closed
* resolution: => invalid
* summary: unique_together uses 'iexact' matching, I expected this to be
'exact' => unique_together on SQLite uses
'iexact' matching, I expected this to be
'exact'
Comment:
Hi Bastian, I don't think these issues are related other than the case
sensitivity. The original bug here was to do with SQLite's lack of a case
sensitive match, whilst your problem is in the manipulators (which
directly specifies iexact). This is a design issue I think, IMO case
insensitive matches are the most common idea (i.e. we don't want a "Simon"
and a "SImon" in the database), but this might be nice to have as an
option.
Long story short - Can you create a new ticket for this issue?
Thanks :)
Simon
--
Ticket URL: <http://code.djangoproject.com/ticket/2422#comment:8>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
