Changes between Initial Version and Version 1 of Ticket #19441, comment 11


Ignore:
Timestamp:
01/07/2013 04:04:11 AM (2 years ago)
Author:
dyve
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #19441, comment 11

    initial v1  
    33 The only "added weight" you collect by solving it like this is the creation of like-indexes on postgresql when the field is used as a unique identifier and not meant for like searching, The like indexes  would be created but never used. I think this is not a problem, as it is far more important to have a unified way that Django works (again, unique=True implies db_index=True) than to take different database vendors into account when deciding when or not to add db_index=True.
    44
    5 To but it briefly, I'd be in favor of submitting this patch as the final solution for this issue.
     5To put it briefly, I'd be in favor of submitting this patch as the final solution for this issue.
Back to Top